← previous blocknext block →recent activity
Analyzing
Block #96,655,831
14 transactions · 14 stateful · 2026-08-17 02:23:40 UTC
Parallelism
71/100
Blocked
43%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,655,831 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w06w17w28w310w011w113w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1aea5dbe…0f59
0x065c9d…c394
4 touches
1 conflict
0x3a921be0…779c
0x2a68ba…90c5
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x0313aedc…bfaf
0x34b655…2a6f
4 touches
1 conflict
0x0313aedc…bfb0
0x34b655…2a6f
4 touches
1 conflict
0x13fa8d63…ba0d
0x34b655…2a6f
4 touches
1 conflict
0x40a9339c…6572
0x34b655…2a6f
4 touches
1 conflict
0x433ec3a1…a1e8
0x34b655…2a6f
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
1 conflict on slot 0x1aea5dbee4…d60f59
Audit this contract →
← previous block·next block →recent activity