← previous blocknext block →recent activity
Analyzing
Block #99,490,286
16 transactions · 14 stateful · 2026-08-27 02:00:50 UTC
Parallelism
88/100
Blocked
36%
Avg conflicts / tx
0.31
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,490,286 · 16 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
1w03w15w06w110w011w113w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xefc629e7…776d
0xa6afd3…d132
4 touches
1 conflict
0x3703b3c0…5695
0x34b655…2a6f
4 touches
1 conflict
0x5c455afd…ce06
0x34b655…2a6f
4 touches
1 conflict
0x948836ff…59ab
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
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-WETH/USDC
1 conflict on slot 0xefc629e7c6…39776d
Audit this contract →
← previous block·next block →recent activity