← previous blocknext block →recent activity
Analyzing
Block #87,122,787
11 transactions · 11 stateful · 2026-07-11 20:07:49 UTC
Parallelism
64/100
Blocked
27%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,122,787 · 11 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
2w03w16w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x19292fad…ec5b
0x34b655…2a6f
6 touches
3 conflicts
0x3133f94b…f76b
0x34b655…2a6f
6 touches
3 conflicts
0x27d7b15f…e839
0x34b655…2a6f
4 touches
1 conflict
0x30adea6d…8391
0x34b655…2a6f
4 touches
1 conflict
0x5e02109f…c11b
0x34b655…2a6f
4 touches
1 conflict
0x727fbce7…0c80
0x34b655…2a6f
4 touches
1 conflict
0x8165b845…efcb
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
3 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity