← previous blocknext block →recent activity
Analyzing
Block #86,924,318
16 transactions · 14 stateful · 2026-07-10 22:01:58 UTC
Parallelism
75/100
Blocked
29%
Avg conflicts / tx
0.31
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,924,318 · 16 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
1w02w14w05w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe718f3c7…c376
0x34b655…2a6f
6 touches
3 conflicts
0x4e10ffaa…5365
0x34b655…2a6f
6 touches
3 conflicts
0x07cfaa71…4085
0x34b655…2a6f
4 touches
1 conflict
0x322fb0e8…962d
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x775a8ad3…8307
0x34b655…2a6f
4 touches
1 conflict
0x8ca13937…b3ce
0x34b655…2a6f
4 touches
1 conflict
0x8cd0745d…4dc0
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 0xe718f3c792…72c376
Audit this contract →
← previous block·next block →recent activity