← previous blocknext block →recent activity
Analyzing
Block #82,665,161
10 transactions · 8 stateful · 2026-06-21 04:20:13 UTC
Parallelism
80/100
Blocked
13%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #82,665,161 · 10 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ccd9546…6ad5
0x065c9d…c394
4 touches
1 conflict
0xd8dd03ce…dc8d
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x07d64d54…6bfc
0x2ab50b…5c41
2 touches
0 conflicts
0x163ef1ec…8e38
0x2ab50b…5c41
2 touches
0 conflicts
0x1bf0c76c…475d
0x2ab50b…5c41
2 touches
0 conflicts
0x2286470b…84fa
0x2ab50b…5c41
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 0x9ccd95469f…d56ad5
Audit this contract →
← previous block·next block →recent activity