← previous blocknext block →recent activity
Analyzing
Block #80,163,275
78 transactions · 59 stateful · 2026-06-09 14:17:05 UTC
Parallelism
71/100
Blocked
83%
Avg conflicts / tx
4.08
Longest chain
23 deep
Execution timeline
did this block parallelize well?
view
block #80,163,275 · 78 txs across 23 waves · depth 23
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
wave w19
wave w20
wave w21
wave w22
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w419w520w622w733w1634w1735w1853w1954w2055w2156w2261w22
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
32 touches
120 conflicts
0xe12b32d8…5857
0xd32edf…ff58
23 touches
66 conflicts
0x90f07a4f…d932
0x34b655…2a6f
22 touches
55 conflicts
0x00000000…003d
0xa6afd3…d132
20 touches
45 conflicts
0xbaff104b…3edb
0xa6afd3…d132
20 touches
45 conflicts
0x40970e69…da50
0x69df8a…6292
18 touches
36 conflicts
0x00000000…0013
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…0015
0x1b6862…e19c
18 touches
36 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
120 conflicts on slot 0x13a54fa2d3…a35ae3
Audit this contract →
← previous block·next block →recent activity