← previous blocknext block →recent activity
Analyzing
Block #99,874,369
10 transactions · 10 stateful · 2026-08-28 10:27:21 UTC
Parallelism
80/100
Blocked
10%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,874,369 · 10 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
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xb31eb7d3…64eb
0xa6afd3…d132
4 touches
1 conflict
0xc21def1b…c24d
0xa6afd3…d132
4 touches
1 conflict
0x05007162…d3c5
0x34b655…2a6f
2 touches
0 conflicts
0x2130a548…c1de
0x34b655…2a6f
2 touches
0 conflicts
0x23769ebc…c8ed
0x34b655…2a6f
2 touches
0 conflicts
0x2f5c6ab7…20ab
0x34b655…2a6f
2 touches
0 conflicts
0x46e2bb67…d8b3
0x34b655…2a6f
2 touches
0 conflicts
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity