← previous blocknext block →recent activity
Analyzing
Block #84,062,707
9 transactions · 7 stateful · 2026-06-27 15:51:54 UTC
Parallelism
78/100
Blocked
14%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,062,707 · 9 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x045f67ff…616f
0x065c9d…c394
2 touches
0 conflicts
0x1d25ef3b…edda
0x065c9d…c394
2 touches
0 conflicts
0x5a0a7dbd…71a7
0x065c9d…c394
2 touches
0 conflicts
0x8e042dbb…f3a2
0x065c9d…c394
2 touches
0 conflicts
0xaec06d75…a2f5
0x065c9d…c394
2 touches
0 conflicts
0xe79ba45f…c24f
0x065c9d…c394
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity