← previous blocknext block →recent activity
Analyzing
Block #99,288,636
14 transactions · 13 stateful · 2026-08-26 09:05:35 UTC
Parallelism
86/100
Blocked
38%
Avg conflicts / tx
0.36
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,288,636 · 14 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
1w02w03w16w17w110w011w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x0fd2cbc5…476b
0x77d53b…8080
4 touches
1 conflict
0x29104487…7b41
0x77d53b…8080
4 touches
1 conflict
0x29104487…7b42
0x77d53b…8080
4 touches
1 conflict
0x29104487…7b9b
0x77d53b…8080
4 touches
1 conflict
0x467e524d…394a
0x77d53b…8080
4 touches
1 conflict
0x467e524d…39c9
0x77d53b…8080
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity