← previous blocknext block →recent activity
Analyzing
Block #95,807,584
20 transactions · 20 stateful · 2026-08-14 03:16:26 UTC
Parallelism
70/100
Blocked
60%
Avg conflicts / tx
1.6
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,807,584 · 20 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
1w02w13w24w35w06w47w58w39w510w011w112w213w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb79f2886…deff
0x065c9d…c394
10 touches
10 conflicts
0x002fed35…79fa
0x2a68ba…90c5
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x7de57974…f5ba
0x34b655…2a6f
6 touches
3 conflicts
0xe8eae8a3…bacc
0x34b655…2a6f
6 touches
3 conflicts
0x4efae872…6aa8
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0xb79f2886dc…13deff
Audit this contract →
← previous block·next block →recent activity