← previous blocknext block →recent activity
Analyzing
Block #81,632,722
15 transactions · 9 stateful · 2026-06-16 09:30:27 UTC
Parallelism
87/100
Blocked
22%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #81,632,722 · 15 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
1w06w112w013w1
- 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
0xb9b4eff6…c3ef
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x04e2faf2…42cc
0x065c9d…c394
2 touches
0 conflicts
0x1b24c961…9ed1
0x065c9d…c394
2 touches
0 conflicts
0x3642472e…efc6
0x065c9d…c394
2 touches
0 conflicts
0xd8dd03ce…dc8d
0x2a68ba…90c5
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