← previous blocknext block →recent activity
Analyzing
Block #84,063,852
18 transactions · 16 stateful · 2026-06-27 15:59:31 UTC
Parallelism
83/100
Blocked
31%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,063,852 · 18 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
1w05w06w19w113w114w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b16149e…7d4d
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0xc8f1adbe…10da
0x065c9d…c394
3 touches
1 conflict
0x7229e25a…82a5
0xd32edf…ff58
3 touches
1 conflict
0xecc8ff01…113e
0x0594c7…a3be
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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 0x0b16149e0d…887d4d
Audit this contract →
← previous block·next block →recent activity