← previous blocknext block →recent activity
Analyzing
Block #81,632,560
11 transactions · 8 stateful · 2026-06-16 09:29:22 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #81,632,560 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x52e69143…95ad
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xd364a7f3…7fc6
0x2a68ba…90c5
4 touches
1 conflict
0xce827910…ff22
0x065c9d…c394
4 touches
1 conflict
0x8e8da811…826f
0x065c9d…c394
4 touches
1 conflict
0x90f57a39…3736
0x065c9d…c394
3 touches
1 conflict
0x46ea094a…6cab
0x065c9d…c394
3 touches
1 conflict
0xdc870d88…874a
0x065c9d…c394
3 touches
1 conflict
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
6 conflicts on slot 0x52e6914362…6e95ad
Audit this contract →
← previous block·next block →recent activity