← previous blocknext block →recent activity
Analyzing
Block #96,449,962
16 transactions · 16 stateful · 2026-08-16 09:07:54 UTC
Parallelism
38/100
Blocked
63%
Avg conflicts / tx
2.88
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #96,449,962 · 16 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w17w28w39w410w511w612w713w814w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…000f
0x78999c…f371
20 touches
45 conflicts
0x00000000…000b
0x754704…b603
20 touches
45 conflicts
0x34b1e500…7687
0x754704…b603
20 touches
45 conflicts
0x00000000…000b
0x78999c…f371
20 touches
45 conflicts
0xe0659a3f…90d9
0x000000…a032
20 touches
45 conflicts
0x89999c15…fdac
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x0460135c…98fd
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: 0x78999cc9…3cf371
45 conflicts on slot 0x0000000000…00000f
Audit this contract →
← previous block·next block →recent activity