← previous blocknext block →recent activity
Analyzing
Block #99,320,291
19 transactions · 17 stateful · 2026-08-26 11:44:48 UTC
Parallelism
68/100
Blocked
53%
Avg conflicts / tx
1.16
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,320,291 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w16w17w29w311w213w314w415w518w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
12 touches
15 conflicts
0xa366dc41…b2d8
0xa6afd3…d132
10 touches
10 conflicts
0xc8ab31f9…8ce9
0xa6afd3…d132
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x91c76829…3407
0xa6afd3…d132
5 touches
3 conflicts
0xe2263bea…6a9d
0x2b46c0…1669
4 touches
1 conflict
0xe2263bea…6a9e
0x2b46c0…1669
4 touches
1 conflict
0xe2263bea…6aa1
0x2b46c0…1669
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
15 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity