← previous blocknext block →recent activity
Analyzing
Block #96,666,393
13 transactions · 11 stateful · 2026-08-17 03:16:47 UTC
Parallelism
77/100
Blocked
18%
Avg conflicts / tx
0.15
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,666,393 · 13 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
5w06w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcd26fba5…21c6
0x34b655…2a6f
4 touches
1 conflict
0xe0e00683…e335
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x59a07ac0…728d
0x34b655…2a6f
4 touches
1 conflict
0x45f562b2…9294
0x2b46c0…1669
2 touches
0 conflicts
0x8488f10f…9353
0x2b46c0…1669
2 touches
0 conflicts
0x8488f10f…9354
0x2b46c0…1669
2 touches
0 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: Perpl
1 conflict on slot 0xcd26fba530…bd21c6
Audit this contract →
← previous block·next block →recent activity