← previous blocknext block →recent activity
Analyzing
Block #86,531,403
18 transactions · 16 stateful · 2026-07-09 02:13:20 UTC
Parallelism
78/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,531,403 · 18 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
1w02w15w06w17w28w39w312w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a35acfb…d1a7
0xb1dbf0…c0d3
8 touches
6 conflicts
0x8a35acfb…d1a6
0xb1dbf0…c0d3
6 touches
3 conflicts
0xc009105d…96f7
0xb1dbf0…c0d3
4 touches
1 conflict
0xf07207b3…cefc
0xb1dbf0…c0d3
4 touches
1 conflict
0x3230277c…ef39
0xc8689a…ee79
4 touches
1 conflict
0x92b49f44…ee4f
0x34b655…2a6f
4 touches
1 conflict
0xb43d23aa…1bd5
0x34b655…2a6f
4 touches
1 conflict
0xd99c922e…5ca0
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: 0xb1dbf05f…b1c0d3
6 conflicts on slot 0x8a35acfbc1…6bd1a7
Audit this contract →
← previous block·next block →recent activity