← previous blocknext block →recent activity
Analyzing
Block #87,592,963
17 transactions · 14 stateful · 2026-07-14 00:33:25 UTC
Parallelism
82/100
Blocked
36%
Avg conflicts / tx
0.41
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,592,963 · 17 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
2w04w05w18w19w010w111w216w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x02679875…8d2f
0x34b655…2a6f
6 touches
3 conflicts
0x05daa16f…c19a
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x0f69f34e…c78e
0x34b655…2a6f
4 touches
1 conflict
0x1175233a…64e7
0x34b655…2a6f
4 touches
1 conflict
0x1da734d0…414e
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x41fc2b04…2805
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 0x0267987539…238d2f
Audit this contract →
← previous block·next block →recent activity