← previous blocknext block →recent activity
Analyzing
Block #96,589,936
18 transactions · 14 stateful · 2026-08-16 20:52:15 UTC
Parallelism
61/100
Blocked
50%
Avg conflicts / tx
1.17
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,589,936 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w26w37w010w411w512w617w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x18978822…2623
0x34b655…2a6f
12 touches
15 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x7b55198a…b946
0x34b655…2a6f
4 touches
1 conflict
0x8f505b3d…6aba
0x34b655…2a6f
4 touches
1 conflict
0x9465bae8…d3ac
0x34b655…2a6f
4 touches
1 conflict
0x9c0cdadd…1574
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
15 conflicts on slot 0x18978822b6…2c2623
Audit this contract →
← previous block·next block →recent activity