← previous blocknext block →recent activity
Analyzing
Block #84,029,266
18 transactions · 13 stateful · 2026-06-27 12:09:10 UTC
Parallelism
89/100
Blocked
8%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,029,266 · 18 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
1w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x20f11164…385e
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf01bd758…e350
0x065c9d…c394
3 touches
1 conflict
0x022dc6b8…7130
0x065c9d…c394
2 touches
0 conflicts
0x0b16149e…7d4d
0x065c9d…c394
2 touches
0 conflicts
0x9f27aa93…49ca
0x065c9d…c394
2 touches
0 conflicts
0x6f6fc26c…3e34
0x34b655…2a6f
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
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 0x20f1116448…39385e
Audit this contract →
← previous block·next block →recent activity