← previous blocknext block →recent activity
Analyzing
Block #96,450,090
10 transactions · 9 stateful · 2026-08-16 09:08:33 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,450,090 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xae6b6f0b…607c
0x968279…9342
4 touches
1 conflict
0x4a1de7fe…95cf
0x968279…9342
4 touches
1 conflict
0x4a1de7fe…95d0
0x968279…9342
4 touches
1 conflict
0x4a1de7fe…95d3
0x968279…9342
4 touches
1 conflict
0x4a1de7fe…95d4
0x968279…9342
4 touches
1 conflict
0x4a1de7fe…95d6
0x968279…9342
4 touches
1 conflict
0xae6b6f0b…6079
0x968279…9342
4 touches
1 conflict
0xae6b6f0b…607a
0x968279…9342
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: 0x96827978…f09342
1 conflict on slot 0xae6b6f0bc6…c8607c
Audit this contract →
← previous block·next block →recent activity