← previous blocknext block →recent activity
Analyzing
Block #84,357,426
11 transactions · 10 stateful · 2026-06-29 00:35:08 UTC
Parallelism
73/100
Blocked
20%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,357,426 · 11 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
1w06w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56785e37…a197
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x020b4000…07a8
0x065c9d…c394
2 touches
0 conflicts
0x6a712218…4c32
0x065c9d…c394
2 touches
0 conflicts
0x910a1a7d…dba0
0x065c9d…c394
2 touches
0 conflicts
0x967312dc…206b
0x065c9d…c394
2 touches
0 conflicts
0xa24d5eb9…0d83
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 0x56785e3778…33a197
Audit this contract →
← previous block·next block →recent activity