← previous blocknext block →recent activity
Analyzing
Block #82,268,540
25 transactions · 21 stateful · 2026-06-19 08:10:58 UTC
Parallelism
76/100
Blocked
38%
Avg conflicts / tx
0.84
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #82,268,540 · 25 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
1w07w18w09w212w313w415w016w117w218w523w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x5540f956…69e8
0x065c9d…c394
8 touches
6 conflicts
0x64d76184…af55
0x34b655…2a6f
6 touches
3 conflicts
0x08913286…f0df
0x34b655…2a6f
6 touches
3 conflicts
0x033cf007…136d
0x34b655…2a6f
6 touches
3 conflicts
0xb665ffc5…d222
0xc8689a…ee79
4 touches
1 conflict
0x9ff176a9…152e
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity