← previous blocknext block →recent activity
Analyzing
Block #84,364,708
22 transactions · 19 stateful · 2026-06-29 01:23:42 UTC
Parallelism
77/100
Blocked
53%
Avg conflicts / tx
0.86
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,364,708 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w07w18w210w011w112w213w314w315w417w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xab86573c…682e
0x34b655…2a6f
8 touches
6 conflicts
0xe75cebb6…6b36
0x065c9d…c394
8 touches
6 conflicts
0x56785e37…a197
0x065c9d…c394
6 touches
3 conflicts
0x431f59a6…a342
0x34b655…2a6f
4 touches
1 conflict
0x5138188e…796b
0x34b655…2a6f
4 touches
1 conflict
0x75291f8b…3ac0
0x34b655…2a6f
4 touches
1 conflict
0x97d5efed…1aa4
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity