← previous blocknext block →recent activity
Analyzing
Block #87,056,424
9 transactions · 7 stateful · 2026-07-11 12:44:40 UTC
Parallelism
67/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,056,424 · 9 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
5w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x83bf1cc7…260e
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xc36fa358…24cb
0x34b655…2a6f
4 touches
1 conflict
0xb4b8c5b1…836b
0x34b655…2a6f
4 touches
1 conflict
0x08682688…53b3
0x34b655…2a6f
2 touches
0 conflicts
0x0e52d81f…461e
0x34b655…2a6f
2 touches
0 conflicts
0x66059cf4…bf4d
0x34b655…2a6f
2 touches
0 conflicts
0x7139bf32…c881
0x34b655…2a6f
2 touches
0 conflicts
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 0x83bf1cc7fb…18260e
Audit this contract →
← previous block·next block →recent activity