← previous blocknext block →recent activity
Analyzing
Block #84,323,505
29 transactions · 24 stateful · 2026-06-28 20:49:02 UTC
Parallelism
69/100
Blocked
71%
Avg conflicts / tx
1.45
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #84,323,505 · 29 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w07w18w19w211w212w313w315w116w418w519w224w425w526w628w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xab86573c…682e
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0x56785e37…a197
0x065c9d…c394
8 touches
6 conflicts
0x070a562a…8147
0x34b655…2a6f
6 touches
3 conflicts
0x0ee4fe41…9382
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity