← previous blocknext block →recent activity
Analyzing
Block #96,685,524
9 transactions · 8 stateful · 2026-08-17 04:53:00 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,685,524 · 9 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
1w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x642d63b7…74c5
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xce7a5e29…65a7
0x065c9d…c394
3 touches
1 conflict
0xd811da43…212f
0x065c9d…c394
3 touches
1 conflict
0xfacc9ebd…065c
0x065c9d…c394
3 touches
1 conflict
0x7e62c5be…77f3
0x065c9d…c394
3 touches
1 conflict
0xa275d4b4…3ce2
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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 0x642d63b781…e274c5
Audit this contract →
← previous block·next block →recent activity