← previous blocknext block →recent activity
Analyzing
Block #80,165,384
29 transactions · 22 stateful · 2026-06-09 14:31:10 UTC
Parallelism
69/100
Blocked
55%
Avg conflicts / tx
1
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #80,165,384 · 29 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w48w49w510w611w718w019w120w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
10 touches
10 conflicts
0x3af0dd8e…0027
0x1b6862…e19c
8 touches
6 conflicts
0x179fe783…6945
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x4fe8d24a…ad63
0xd32edf…ff58
7 touches
6 conflicts
0x426ef19c…a68b
0x065c9d…c394
7 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 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
10 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity