← previous blocknext block →recent activity
Analyzing
Block #86,629,065
23 transactions · 19 stateful · 2026-07-09 13:07:50 UTC
Parallelism
87/100
Blocked
42%
Avg conflicts / tx
0.39
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,629,065 · 23 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w07w18w19w010w111w113w214w218w020w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xfe2b47…c052
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x4a4c3d20…bd65
0x3bd359…433a
4 touches
1 conflict
0x0db0aaac…e94d
0x43cf54…7777
4 touches
1 conflict
0x00000000…0000
0x4a92f8…f3d6
4 touches
1 conflict
0x00000000…0001
0x4a92f8…f3d6
4 touches
1 conflict
0x421c32c1…4629
0x754704…b603
4 touches
1 conflict
0x5a1cd68f…4125
0x754704…b603
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: 0xfe2b47e2…5cc052
3 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity