← previous blocknext block →recent activity
Analyzing
Block #81,629,567
14 transactions · 12 stateful · 2026-06-16 09:09:26 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #81,629,567 · 14 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
1w02w17w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ea9c1d6…6d1c
0x065c9d…c394
4 touches
1 conflict
0x90f07a4f…d932
0x34b655…2a6f
4 touches
1 conflict
0x0b34f052…a4c8
0x065c9d…c394
3 touches
1 conflict
0xf0aceec7…95ad
0x065c9d…c394
3 touches
1 conflict
0x1b24c961…9ed1
0x065c9d…c394
2 touches
0 conflicts
0xaf7c4e2f…2922
0x065c9d…c394
2 touches
0 conflicts
0xce827910…ff22
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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 0x0ea9c1d681…256d1c
Audit this contract →
← previous block·next block →recent activity