← previous blocknext block →recent activity
Analyzing
Block #86,613,582
19 transactions · 17 stateful · 2026-07-09 11:24:29 UTC
Parallelism
68/100
Blocked
35%
Avg conflicts / tx
0.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,613,582 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w17w28w311w017w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0004
0xb1dbf0…c0d3
8 touches
6 conflicts
0x8a35acfb…d1a9
0xb1dbf0…c0d3
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1aa
0xb1dbf0…c0d3
7 touches
6 conflicts
0xf7e59d30…11dd
0x34b655…2a6f
6 touches
3 conflicts
0x07b979bc…3564
0xb1dbf0…c0d3
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xa29182a1…c12c
0x34b655…2a6f
6 touches
3 conflicts
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 0x0000000000…000004
Audit this contract →
← previous block·next block →recent activity