← previous blocknext block →recent activity
Analyzing
Block #96,612,916
13 transactions · 10 stateful · 2026-08-16 22:47:50 UTC
Parallelism
77/100
Blocked
40%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,612,916 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w08w19w211w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xce06a0f7…efef
0x34b655…2a6f
5 touches
3 conflicts
0x52ff8fec…18d2
0x34b655…2a6f
5 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x5950f4ea…90fd
0x34b655…2a6f
4 touches
1 conflict
0x5540f956…69e8
0x065c9d…c394
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: Kuru Exchange: Market-MON/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity