← previous blocknext block →recent activity
Analyzing
Block #83,868,841
24 transactions · 23 stateful · 2026-06-26 18:20:06 UTC
Parallelism
67/100
Blocked
48%
Avg conflicts / tx
0.83
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #83,868,841 · 24 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w06w07w18w09w111w112w213w315w116w417w418w521w622w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0018
0x1b6862…e19c
6 touches
3 conflicts
0xcb45d9d6…cb80
0x1b6862…e19c
6 touches
3 conflicts
0xff96dc9b…93d7
0x065c9d…c394
6 touches
3 conflicts
0xf9c7f2ae…f91e
0xd32edf…ff58
5 touches
3 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: MarginAccount
6 conflicts on slot 0x046a928e85…e50012
Audit this contract →
← previous block·next block →recent activity