← previous blocknext block →recent activity
Analyzing
Block #96,490,630
16 transactions · 13 stateful · 2026-08-16 12:32:29 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,490,630 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w26w37w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbffde283…3385
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x038b9243…553d
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x94fd809f…6934
0x34b655…2a6f
4 touches
1 conflict
0x0e215b60…b3bb
0x754704…b603
2 touches
0 conflicts
0x3b38d05d…df00
0x754704…b603
2 touches
0 conflicts
0x66c70a3f…1e9c
0x754704…b603
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
6 conflicts on slot 0xbffde283d8…c63385
Audit this contract →
← previous block·next block →recent activity