← previous blocknext block →recent activity
Analyzing
Block #82,727,584
23 transactions · 20 stateful · 2026-06-21 11:17:07 UTC
Parallelism
65/100
Blocked
60%
Avg conflicts / tx
1.3
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #82,727,584 · 23 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
1w02w13w24w36w27w08w39w410w412w513w614w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x14149f52…7320
0xd32edf…ff58
7 touches
6 conflicts
0xf9f48af5…4205
0xa6afd3…d132
6 touches
3 conflicts
0x26470289…bb21
0xa6afd3…d132
6 touches
3 conflicts
0x5d46e6a0…5ed9
0x40c49f…2af0
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x580c6fe7…0fe3
0x1b6862…e19c
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: MarginAccount
10 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity