← previous blocknext block →recent activity
Analyzing
Block #96,522,748
9 transactions · 9 stateful · 2026-08-16 15:14:19 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
0.78
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,522,748 · 9 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
1w02w03w14w26w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe999cbf5…d18a
0x34b655…2a6f
6 touches
3 conflicts
0xc5a78c51…2753
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x86c98782…f3b7
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x57be321f…fecc
0x34b655…2a6f
4 touches
1 conflict
0x17935a8f…a796
0x34b655…2a6f
4 touches
1 conflict
0x82dd2252…e1ce
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
3 conflicts on slot 0xe999cbf59e…59d18a
Audit this contract →
← previous block·next block →recent activity