← previous blocknext block →recent activity
Analyzing
Block #96,212,822
17 transactions · 13 stateful · 2026-08-15 13:15:13 UTC
Parallelism
53/100
Blocked
54%
Avg conflicts / tx
1.59
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #96,212,822 · 17 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w08w29w310w411w512w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
14 touches
21 conflicts
0xea1b8c07…b969
0x34b655…2a6f
12 touches
15 conflicts
0xd5abc901…166d
0x34b655…2a6f
8 touches
6 conflicts
0x514e8c17…48c0
0x34b655…2a6f
8 touches
6 conflicts
0x35c29640…8779
0x34b655…2a6f
6 touches
3 conflicts
0x4ec6412a…4400
0x34b655…2a6f
4 touches
1 conflict
0x6be37e18…14e0
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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity