← previous blocknext block →recent activity
Analyzing
Block #99,473,515
13 transactions · 12 stateful · 2026-08-27 00:36:21 UTC
Parallelism
85/100
Blocked
33%
Avg conflicts / tx
0.46
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,473,515 · 13 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
1w03w04w15w06w17w09w010w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xefc629e7…776d
0xa6afd3…d132
4 touches
1 conflict
0x51af0e92…4020
0x34b655…2a6f
4 touches
1 conflict
0x5ea5b43e…24cc
0x34b655…2a6f
4 touches
1 conflict
0x8f63fda5…b877
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd459bf7b…92c3
0x34b655…2a6f
4 touches
1 conflict
0xea57afd0…4232
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
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