← previous blocknext block →recent activity
Analyzing
Block #86,628,962
21 transactions · 19 stateful · 2026-07-09 13:07:09 UTC
Parallelism
71/100
Blocked
32%
Avg conflicts / tx
0.62
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,628,962 · 21 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
1w02w13w25w39w310w418w019w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x4a92f8…f3d6
8 touches
6 conflicts
0x4a4c3d20…bd65
0x3bd359…433a
8 touches
6 conflicts
0x0db0aaac…e94d
0x43cf54…7777
8 touches
6 conflicts
0x850a22b0…97dd
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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: 0x4a92f8d9…13f3d6
6 conflicts on slot 0x0000000000…000000
Audit this contract →
← previous block·next block →recent activity