← previous blocknext block →recent activity
Analyzing
Block #87,612,371
17 transactions · 13 stateful · 2026-07-14 02:43:12 UTC
Parallelism
76/100
Blocked
54%
Avg conflicts / tx
0.59
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,612,371 · 17 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
1w02w13w25w06w17w29w010w111w312w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd379a368…fea4
0x34b655…2a6f
6 touches
3 conflicts
0x25329a48…4e00
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x1175233a…64e7
0x34b655…2a6f
6 touches
3 conflicts
0x5170a218…3a84
0xc8689a…ee79
6 touches
3 conflicts
0x07b86c51…cdae
0x2a68ba…90c5
4 touches
1 conflict
0xc36fa358…24cb
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 0xd379a36873…4efea4
Audit this contract →
← previous block·next block →recent activity