← previous blocknext block →recent activity
Analyzing
Block #96,276,028
9 transactions · 7 stateful · 2026-08-15 18:33:08 UTC
Parallelism
44/100
Blocked
57%
Avg conflicts / tx
0.89
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,276,028 · 9 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
1w04w15w26w37w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…641f
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
8 touches
6 conflicts
0x4acc6dca…a868
0x34b655…2a6f
7 touches
6 conflicts
0xfc24540b…6463
0x34b655…2a6f
6 touches
3 conflicts
0x3695cc4a…f3d8
0x34b655…2a6f
6 touches
3 conflicts
0x70be0d05…fc4e
0x34b655…2a6f
6 touches
3 conflicts
0x784eaad2…d176
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
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
6 conflicts on slot 0xc824469a90…af641f
Audit this contract →
← previous block·next block →recent activity