← previous blocknext block →recent activity
Analyzing
Block #96,494,380
9 transactions · 5 stateful · 2026-08-16 12:51:20 UTC
Parallelism
78/100
Blocked
20%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,494,380 · 9 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
1w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcf59d5c4…7b64
0x34b655…2a6f
4 touches
1 conflict
0xee8237bd…46ad
0x34b655…2a6f
4 touches
1 conflict
0x07bb3f5a…617e
0x34b655…2a6f
2 touches
0 conflicts
0x11e44201…612d
0x34b655…2a6f
2 touches
0 conflicts
0x367b69ad…33d8
0x34b655…2a6f
2 touches
0 conflicts
0x367b69ad…33d9
0x34b655…2a6f
2 touches
0 conflicts
0x458b9085…9ee2
0x34b655…2a6f
2 touches
0 conflicts
0x524f0872…0d12
0x34b655…2a6f
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 0xcf59d5c48d…e77b64
Audit this contract →
← previous block·next block →recent activity