← previous blocknext block →recent activity
Analyzing
Block #84,068,727
13 transactions · 12 stateful · 2026-06-27 16:31:55 UTC
Parallelism
69/100
Blocked
42%
Avg conflicts / tx
0.62
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,068,727 · 13 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
1w02w03w14w25w17w18w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xff96dc9b…93d7
0x065c9d…c394
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xcb45d9d6…cb84
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…001c
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x6514e777…63ad
0xd32edf…ff58
5 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
4 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
3 conflicts on slot 0xff96dc9b2f…5a93d7
Audit this contract →
← previous block·next block →recent activity