← previous blocknext block →recent activity
Analyzing
Block #96,611,334
12 transactions · 12 stateful · 2026-08-16 22:39:53 UTC
Parallelism
42/100
Blocked
58%
Avg conflicts / tx
1.75
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,611,334 · 12 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
1w02w13w24w35w46w57w510w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd8ef18ea…9294
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xca2926e0…61b5
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xa6311649…0132
0x34b655…2a6f
6 touches
3 conflicts
0xaa1dd7d8…b929
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 0xd8ef18ea01…369294
Audit this contract →
← previous block·next block →recent activity