← previous blocknext block →recent activity
Analyzing
Block #84,247,385
24 transactions · 21 stateful · 2026-06-28 12:21:54 UTC
Parallelism
88/100
Blocked
10%
Avg conflicts / tx
0.17
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,247,385 · 24 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
1w010w016w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56785e37…a197
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x02107c90…9277
0x065c9d…c394
3 touches
1 conflict
0x62af2727…9fa2
0x065c9d…c394
3 touches
1 conflict
0x776b206d…6cf9
0x3bd359…433a
2 touches
0 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
2 touches
0 conflicts
0x78b6c319…bac0
0x3c2269…cf62
2 touches
0 conflicts
0x7a814f0d…35fd
0x3c2269…cf62
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 0x56785e3778…33a197
Audit this contract →
← previous block·next block →recent activity