← previous blocknext block →recent activity
Analyzing
Block #81,630,753
13 transactions · 7 stateful · 2026-06-16 09:17:20 UTC
Parallelism
85/100
Blocked
29%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #81,630,753 · 13 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
1w07w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xce827910…ff22
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x2287538a…aa72
0x065c9d…c394
2 touches
0 conflicts
0x52e69143…95ad
0x065c9d…c394
2 touches
0 conflicts
0x5c2e4677…783a
0x065c9d…c394
2 touches
0 conflicts
0xb027666c…236f
0x065c9d…c394
2 touches
0 conflicts
0xc8fb12f7…fa7e
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 0xce827910a4…82ff22
Audit this contract →
← previous block·next block →recent activity