← previous blocknext block →recent activity
Analyzing
Block #96,495,585
11 transactions · 10 stateful · 2026-08-16 12:57:25 UTC
Parallelism
82/100
Blocked
10%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,495,585 · 11 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
6w07w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd5359d85…0bd8
0x34b655…2a6f
4 touches
1 conflict
0xef879fb4…3aeb
0x34b655…2a6f
4 touches
1 conflict
0xf664f8dc…808f
0x34b655…2a6f
4 touches
1 conflict
0x5fc1d933…62d0
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x8a02d049…f481
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc8c615d4…5da3
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: Perpl
1 conflict on slot 0xd5359d8596…1f0bd8
Audit this contract →
← previous block·next block →recent activity