← previous blocknext block →recent activity
Analyzing
Block #95,810,285
9 transactions · 8 stateful · 2026-08-14 03:30:01 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,810,285 · 9 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5139f7e0…aa09
0x065c9d…c394
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x0778475b…bd75
0x2a68ba…90c5
4 touches
1 conflict
0x0bfc83e5…e8eb
0x34b655…2a6f
2 touches
0 conflicts
0x434f6810…b050
0x34b655…2a6f
2 touches
0 conflicts
0x4c619b7d…f4fa
0x34b655…2a6f
2 touches
0 conflicts
0x4efe356f…22fa
0x34b655…2a6f
2 touches
0 conflicts
0x5da59c2b…d7b2
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 0x5139f7e047…0caa09
Audit this contract →
← previous block·next block →recent activity