← previous blocknext block →recent activity
Analyzing
Block #82,649,196
11 transactions · 7 stateful · 2026-06-21 02:33:06 UTC
Parallelism
82/100
Blocked
14%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #82,649,196 · 11 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
0x317699ec…4c5b
0x065c9d…c394
4 touches
1 conflict
0xe9be541b…1b9e
0x065c9d…c394
3 touches
1 conflict
0xebafb3f4…4b6f
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x5540f956…69e8
0x065c9d…c394
2 touches
0 conflicts
0x786f1e08…bd2b
0x065c9d…c394
2 touches
0 conflicts
0x9ff176a9…152e
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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 0x317699ecb2…144c5b
Audit this contract →
← previous block·next block →recent activity