← previous blocknext block →recent activity
Analyzing
Block #84,495,800
11 transactions · 10 stateful · 2026-06-29 15:57:40 UTC
Parallelism
82/100
Blocked
10%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,495,800 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x460b0bbf…af64
0x065c9d…c394
4 touches
1 conflict
0xf6e9c550…3ce0
0x065c9d…c394
3 touches
1 conflict
0xb20ffddf…cc71
0x065c9d…c394
3 touches
1 conflict
0xe31dd99f…85e1
0x065c9d…c394
2 touches
0 conflicts
0x7d42dc8b…fdb6
0x2a68ba…90c5
2 touches
0 conflicts
0x02923035…8940
0x34b655…2a6f
2 touches
0 conflicts
0x0666358c…c405
0x34b655…2a6f
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
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity