← previous blocknext block →recent activity
Analyzing
Block #99,284,710
15 transactions · 15 stateful · 2026-08-26 08:45:50 UTC
Parallelism
80/100
Blocked
27%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,284,710 · 15 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
1w02w07w111w012w113w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x631b4113…baa9
0x34b655…2a6f
4 touches
1 conflict
0x0fd2cbc5…476b
0x77d53b…8080
4 touches
1 conflict
0x29f3d595…dea7
0x77d53b…8080
4 touches
1 conflict
0x467e524d…39c9
0x77d53b…8080
4 touches
1 conflict
0x85c42e7e…1a25
0x77d53b…8080
4 touches
1 conflict
0x85c42e7e…1a3c
0x77d53b…8080
4 touches
1 conflict
0xa849614b…9f50
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