← previous blocknext block →recent activity
Analyzing
Block #86,804,264
27 transactions · 20 stateful · 2026-07-10 08:39:10 UTC
Parallelism
85/100
Blocked
40%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,804,264 · 27 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
1w05w06w07w110w014w115w117w218w223w125w226w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0x11948993…d61f
0x34b655…2a6f
4 touches
1 conflict
0x150703d8…d519
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x3483ab79…8ed3
0x34b655…2a6f
4 touches
1 conflict
0x44a1b0a6…c9c1
0x34b655…2a6f
4 touches
1 conflict
0x505d32fe…14ad
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity