← previous blocknext block →recent activity
Analyzing
Block #96,684,974
10 transactions · 9 stateful · 2026-08-17 04:50:14 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,684,974 · 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
1w05w07w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2886e2bc…6ab8
0x065c9d…c394
4 touches
1 conflict
0x3d93ad2c…e747
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xf9444acb…193d
0x34b655…2a6f
4 touches
1 conflict
0xa94c39e8…205f
0x065c9d…c394
3 touches
1 conflict
0x489cb750…7069
0x065c9d…c394
2 touches
0 conflicts
0x731e6d82…2883
0x065c9d…c394
2 touches
0 conflicts
0xe9beb382…60c4
0x065c9d…c394
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 0x2886e2bc57…316ab8
Audit this contract →
← previous block·next block →recent activity