← previous blocknext block →recent activity
Analyzing
Block #96,697,564
13 transactions · 13 stateful · 2026-08-17 05:53:34 UTC
Parallelism
54/100
Blocked
46%
Avg conflicts / tx
1.46
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,697,564 · 13 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w26w37w410w512w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3f2796bf…f0fa
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xe9452241…95a3
0x34b655…2a6f
8 touches
6 conflicts
0x07bb3f5a…617e
0x34b655…2a6f
6 touches
3 conflicts
0x4c619b7d…f4fa
0x34b655…2a6f
6 touches
3 conflicts
0x5906754f…b584
0x34b655…2a6f
6 touches
3 conflicts
0x9cf9008a…d826
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x3f2796bf67…faf0fa
Audit this contract →
← previous block·next block →recent activity