← previous blocknext block →recent activity
Analyzing
Block #84,363,854
17 transactions · 16 stateful · 2026-06-29 01:18:02 UTC
Parallelism
76/100
Blocked
25%
Avg conflicts / tx
0.35
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,363,854 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w010w111w212w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x56785e37…a197
0x065c9d…c394
4 touches
1 conflict
0x1a6fe3c2…8ab0
0x065c9d…c394
2 touches
0 conflicts
0x24396344…fa80
0x065c9d…c394
2 touches
0 conflicts
0xa3e53b41…ad72
0x065c9d…c394
2 touches
0 conflicts
0xb7843c24…a6fb
0x065c9d…c394
2 touches
0 conflicts
0xbd87d610…6da7
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity