← previous blocknext block →recent activity
Analyzing
Block #96,362,716
10 transactions · 8 stateful · 2026-08-16 01:49:08 UTC
Parallelism
80/100
Blocked
13%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,362,716 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1ad2a5a5…6575
0x065c9d…c394
4 touches
1 conflict
0x9ff176a9…152e
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x9acdfa49…6b50
0x065c9d…c394
3 touches
1 conflict
0x180397c3…7483
0x065c9d…c394
3 touches
1 conflict
0x76c4467d…ce28
0x34b655…2a6f
2 touches
0 conflicts
0xc2db6e7a…d074
0x34b655…2a6f
2 touches
0 conflicts
0xf726e2e2…e561
0x34b655…2a6f
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: Kuru Exchange: Market-MON/USDC
1 conflict on slot 0x1ad2a5a55f…ab6575
Audit this contract →
← previous block·next block →recent activity