← previous blocknext block →recent activity
Analyzing
Block #99,253,522
24 transactions · 22 stateful · 2026-08-26 06:08:52 UTC
Parallelism
88/100
Blocked
32%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,253,522 · 24 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
1w02w04w05w06w17w012w113w216w117w118w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x27ff4c40…6e37
0x065c9d…c394
5 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0xe7f59f1b…fb6c
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x7e80192b…b958
0x40c49f…2af0
4 touches
1 conflict
0xd08db6ee…a943
0x40c49f…2af0
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 0x27ff4c40e7…426e37
Audit this contract →
← previous block·next block →recent activity