← previous blocknext block →recent activity
Analyzing
Block #84,624,616
12 transactions · 11 stateful · 2026-06-30 06:16:45 UTC
Parallelism
67/100
Blocked
27%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,624,616 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf28082df…312c
0x34b655…2a6f
6 touches
4 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
6 touches
3 conflicts
0x2fdfa032…139c
0x34b655…2a6f
4 touches
1 conflict
0x32409e80…a396
0x34b655…2a6f
4 touches
1 conflict
0x57be321f…fecc
0x34b655…2a6f
4 touches
1 conflict
0x5859dbdc…b42c
0x34b655…2a6f
4 touches
1 conflict
0x5f447bf3…57c7
0x34b655…2a6f
4 touches
1 conflict
0x634daab4…dd5e
0x34b655…2a6f
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
4 conflicts on slot 0xf28082df38…4b312c
Audit this contract →
← previous block·next block →recent activity