← previous blocknext block →recent activity
Analyzing
Block #82,978,718
11 transactions · 6 stateful · 2026-06-22 15:14:57 UTC
Parallelism
82/100
Blocked
17%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #82,978,718 · 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x80afd9d9…57cf
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x299264e9…d925
0x065c9d…c394
2 touches
0 conflicts
0x32feab71…e748
0x065c9d…c394
2 touches
0 conflicts
0x379c5d4e…3e93
0x065c9d…c394
2 touches
0 conflicts
0x95650e0d…2df8
0x065c9d…c394
2 touches
0 conflicts
0xc95aae0e…23d7
0x065c9d…c394
2 touches
0 conflicts
0xcce334a6…06ec
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 0x80afd9d9f2…3f57cf
Audit this contract →
← previous block·next block →recent activity