← previous blocknext block →recent activity
Analyzing
Block #99,481,200
18 transactions · 17 stateful · 2026-08-27 01:15:05 UTC
Parallelism
83/100
Blocked
53%
Avg conflicts / tx
0.67
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,481,200 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w06w19w010w211w112w213w214w115w216w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x31f1efce…7865
0x34b655…2a6f
6 touches
3 conflicts
0x920754e8…0ac6
0x34b655…2a6f
6 touches
3 conflicts
0xb5924647…4cf1
0x34b655…2a6f
6 touches
3 conflicts
0x8ff85b19…dde0
0x34b655…2a6f
4 touches
1 conflict
0x904e2bfb…1544
0x34b655…2a6f
4 touches
1 conflict
0xb3a1165e…2b84
0x34b655…2a6f
4 touches
1 conflict
0xb31eb7d3…64eb
0xa6afd3…d132
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity