← previous blocknext block →recent activity
Analyzing
Block #96,624,450
14 transactions · 13 stateful · 2026-08-16 23:45:50 UTC
Parallelism
64/100
Blocked
54%
Avg conflicts / tx
1.14
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,624,450 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w36w18w09w210w012w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x731e6d82…2883
0x065c9d…c394
8 touches
6 conflicts
0xcdc1731c…b91a
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
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
6 conflicts on slot 0x731e6d8269…072883
Audit this contract →
← previous block·next block →recent activity