← previous blocknext block →recent activity
Analyzing
Block #95,759,404
14 transactions · 12 stateful · 2026-08-13 23:14:07 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,759,404 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w26w37w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x215f5e75…82d0
0x065c9d…c394
7 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x0778475b…bd75
0x2a68ba…90c5
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x22fa50ef…5c35
0x065c9d…c394
2 touches
0 conflicts
0x8e66bb9c…194b
0x065c9d…c394
2 touches
0 conflicts
0xa225050a…5803
0x065c9d…c394
2 touches
0 conflicts
0x00000000…009a
0x16f70c…c3dd
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
6 conflicts on slot 0x215f5e7502…f682d0
Audit this contract →
← previous block·next block →recent activity