← previous blocknext block →recent activity
Analyzing
Block #84,067,019
13 transactions · 10 stateful · 2026-06-27 16:20:33 UTC
Parallelism
77/100
Blocked
30%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,067,019 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w18w29w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x0b16149e…7d4d
0x065c9d…c394
4 touches
1 conflict
0x1be4c2d9…b015
0x065c9d…c394
4 touches
1 conflict
0x022dc6b8…7130
0x065c9d…c394
3 touches
1 conflict
0x52693543…e142
0x065c9d…c394
3 touches
1 conflict
0x8a05248a…9848
0x065c9d…c394
3 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002c
0x1b6862…e19c
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity