← previous blocknext block →recent activity
Analyzing
Block #99,194,260
16 transactions · 16 stateful · 2026-08-26 01:10:42 UTC
Parallelism
88/100
Blocked
6%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,194,260 · 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
9w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3f2100d8…f9b5
0xa6afd3…d132
4 touches
1 conflict
0x7ea1cfdf…81c0
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x085df2c1…305a
0x34b655…2a6f
2 touches
0 conflicts
0x126c10ea…a328
0x34b655…2a6f
2 touches
0 conflicts
0x199a4f01…2183
0x34b655…2a6f
2 touches
0 conflicts
0x1a9478a1…7758
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 0x3f2100d80a…98f9b5
Audit this contract →
← previous block·next block →recent activity