← previous blocknext block →recent activity
Analyzing
Block #99,134,994
11 transactions · 8 stateful · 2026-08-25 20:12:32 UTC
Parallelism
82/100
Blocked
25%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,134,994 · 11 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
5w06w17w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x02180689…6adc
0x065c9d…c394
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0x4b4d6af5…02f7
0xe52b14…7230
3 touches
1 conflict
0x90a021f0…f922
0x34b655…2a6f
2 touches
0 conflicts
0x9b0d7e85…696e
0x34b655…2a6f
2 touches
0 conflicts
0x9b65f692…2bb2
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-MON/USDC
1 conflict on slot 0x021806897f…406adc
Audit this contract →
← previous block·next block →recent activity