← previous blocknext block →recent activity
Analyzing
Block #93,511,111
14 transactions · 13 stateful · 2026-08-06 02:13:26 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,511,111 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6b9bb4b…145a
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x9ba6ae4a…90cb
0x34b655…2a6f
4 touches
1 conflict
0x1c795b3a…8e8a
0x754704…b603
4 touches
1 conflict
0x3a473699…6159
0x754704…b603
4 touches
1 conflict
0xde8a9295…0466
0x754704…b603
4 touches
1 conflict
0xa9fde395…e204
0x99c7a7…8bf0
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
1 conflict on slot 0xc6b9bb4b8d…cc145a
Audit this contract →
← previous block·next block →recent activity