← previous blocknext block →recent activity
Analyzing
Block #84,359,085
34 transactions · 29 stateful · 2026-06-29 00:46:14 UTC
Parallelism
79/100
Blocked
62%
Avg conflicts / tx
1.06
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #84,359,085 · 34 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w06w17w28w09w110w212w013w114w215w318w219w320w423w130w432w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x454d8940…cfe7
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0xd637b3…4160
6 touches
3 conflicts
0x56785e37…a197
0x065c9d…c394
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x0a82ef74…6501
0x34b655…2a6f
6 touches
3 conflicts
0xc08384da…ecb7
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