← previous blocknext block →recent activity
Analyzing
Block #84,083,308
16 transactions · 13 stateful · 2026-06-27 18:09:05 UTC
Parallelism
88/100
Blocked
8%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,083,308 · 16 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
1w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac3aa0aa…9def
0x065c9d…c394
4 touches
1 conflict
0x3185518b…3af9
0x065c9d…c394
3 touches
1 conflict
0x0991a793…ead2
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0xe9fa282e…b9fb
0x065c9d…c394
2 touches
0 conflicts
0xff96dc9b…93d7
0x065c9d…c394
2 touches
0 conflicts
0x046a928e…0012
0x2a68ba…90c5
2 touches
0 conflicts
0x22e0cc1d…ad04
0x34b655…2a6f
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 0xac3aa0aab5…289def
Audit this contract →
← previous block·next block →recent activity