← previous blocknext block →recent activity
Analyzing
Block #82,524,870
14 transactions · 11 stateful · 2026-06-20 12:40:49 UTC
Parallelism
79/100
Blocked
18%
Avg conflicts / tx
0.14
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #82,524,870 · 14 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
1w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2ee3a641…f9b2
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xd8dd03ce…dc8d
0x2a68ba…90c5
4 touches
1 conflict
0x19380c04…fe20
0x065c9d…c394
3 touches
1 conflict
0x9476b160…1e7d
0x065c9d…c394
3 touches
1 conflict
0x8dd3cce7…2520
0x065c9d…c394
2 touches
0 conflicts
0x8fe039f1…5c56
0x065c9d…c394
2 touches
0 conflicts
0x9ff176a9…152e
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
1 conflict on slot 0x2ee3a6414b…6df9b2
Audit this contract →
← previous block·next block →recent activity