← previous blocknext block →recent activity
Analyzing
Block #84,530,053
26 transactions · 22 stateful · 2026-06-29 19:46:07 UTC
Parallelism
77/100
Blocked
41%
Avg conflicts / tx
0.58
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,530,053 · 26 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w011w012w113w115w216w317w418w523w124w225w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x0b16149e…7d4d
0x065c9d…c394
8 touches
6 conflicts
0x61d79ecb…7867
0x065c9d…c394
4 touches
1 conflict
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0x56785e37…a197
0x065c9d…c394
4 touches
1 conflict
0x727fbce7…0c80
0x34b655…2a6f
4 touches
1 conflict
0xbd68c7c7…40b3
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity