He used a free tool, DB Browser for SQLite, to open the file. He scrolled through tables with names like handle , message , and chat . In the handle table, he found her: elena.c.88@icloud.com . Her ID was there, untouched. But in the blocked table? He queried: SELECT * FROM blocked; .

He learned a hard truth that night: Apple prioritizes privacy and security over user “peeking.” The block list is intentionally opaque. You cannot see a blocked contact because the system’s job is to pretend they do not exist . To the operating system, a blocked contact is not a hidden file; it is a null reference . When you block someone, the OS stops asking the question, “Should this person be allowed to contact you?” Instead, it simply never looks them up.

He didn’t need to see if Elena had texted him. He needed to know if he still mattered to her. He was using the Mac as a psychic divining rod, hoping that a database query would substitute for a conversation, that a SELECT statement would heal the silence.

He opened the Find My app. If she shared her location before the block, would it still show? No. The block severs that link. Her dot was gone, replaced by the pale gray silhouette of a person who no longer existed in his digital geography.

Arthur, a database architect by trade, knew that data is never truly deleted. It is merely re-labeled. He opened Finder and navigated to ~/Library/Messages/chat.db . This was the heart of iMessage on macOS—a SQLite database containing every message, every attachment, and crucially, every handle that had ever been involved in a conversation.