← previous blocknext block →recent activity
Analyzing
Block #95,084,816
24 transactions · 21 stateful · 2026-08-11 14:26:25 UTC
Parallelism
79/100
Blocked
48%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,084,816 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w06w27w19w310w012w113w015w016w119w220w321w423w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x160f117d…8e90
0x065c9d…c394
8 touches
6 conflicts
0x38bdc5d3…a632
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xb33ff823…1188
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x8c381258…46d0
0x34b655…2a6f
4 touches
1 conflict
0x94de4d05…ad01
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-MON/USDC
6 conflicts on slot 0x160f117d43…518e90
Audit this contract →
← previous block·next block →recent activity