← previous blocknext block →recent activity
Analyzing
Block #95,370,758
21 transactions · 21 stateful · 2026-08-12 14:36:37 UTC
Parallelism
76/100
Blocked
52%
Avg conflicts / tx
1.19
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,370,758 · 21 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
1w02w05w16w07w19w110w211w212w313w414w215w316w420w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x160f117d…8e90
0x065c9d…c394
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0x3439dfbc…0d03
0x34b655…2a6f
8 touches
6 conflicts
0x3e120bda…a807
0x34b655…2a6f
7 touches
6 conflicts
0xb33ff823…1188
0x065c9d…c394
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity