← previous blocknext block →recent activity
Analyzing
Block #84,605,822
18 transactions · 17 stateful · 2026-06-30 04:11:45 UTC
Parallelism
83/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,605,822 · 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
1w02w111w012w013w214w215w117w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56785e37…a197
0x065c9d…c394
6 touches
3 conflicts
0xe3c72d9e…9b35
0x40c49f…2af0
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5f3fc680…f989
0x34b655…2a6f
4 touches
1 conflict
0x5581d709…ab77
0x2a68ba…90c5
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c6
0x1b6862…e19c
4 touches
1 conflict
0xe75cebb6…6b36
0x065c9d…c394
4 touches
1 conflict
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