← previous blocknext block →recent activity
Analyzing
Block #95,405,642
17 transactions · 17 stateful · 2026-08-12 17:33:12 UTC
Parallelism
88/100
Blocked
24%
Avg conflicts / tx
0.24
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,405,642 · 17 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
4w06w07w18w19w010w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x529e53cf…38e4
0xa6afd3…d132
4 touches
1 conflict
0xa4756d36…e7b2
0x968279…9342
4 touches
1 conflict
0xc578b023…58e5
0x968279…9342
4 touches
1 conflict
0xc578b023…58e6
0x968279…9342
4 touches
1 conflict
0xc578b023…58e8
0x968279…9342
4 touches
1 conflict
0xb3572c95…9c4a
0x2a68ba…90c5
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
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 0x529e53cf07…5438e4
Audit this contract →
← previous block·next block →recent activity