← previous blocknext block →recent activity
Analyzing
Block #82,667,831
30 transactions · 19 stateful · 2026-06-21 04:38:05 UTC
Parallelism
90/100
Blocked
16%
Avg conflicts / tx
0.13
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #82,667,831 · 30 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
3w07w113w219w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x80afd9d9…57cf
0x065c9d…c394
4 touches
1 conflict
0x8aedc364…ff2f
0x065c9d…c394
3 touches
1 conflict
0x6624f2de…1c9d
0xd32edf…ff58
3 touches
1 conflict
0x56ac266e…a56b
0x065c9d…c394
2 touches
0 conflicts
0x7cc5cc1a…e1ce
0x065c9d…c394
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity