← previous blocknext block →recent activity
Analyzing
Block #82,685,186
15 transactions · 10 stateful · 2026-06-21 06:34:13 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #82,685,186 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x5540f956…69e8
0x065c9d…c394
4 touches
1 conflict
0x1c0d6b00…aa60
0x065c9d…c394
2 touches
0 conflicts
0x3ba9b4ec…7c8d
0x065c9d…c394
2 touches
0 conflicts
0x408bf265…84f6
0x065c9d…c394
2 touches
0 conflicts
0x58de60ad…21bb
0x065c9d…c394
2 touches
0 conflicts
0x606fb1f3…f043
0x065c9d…c394
2 touches
0 conflicts
0x9e8212be…1d40
0x065c9d…c394
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity