← previous blocknext block →recent activity
Analyzing
Block #80,401,209
22 transactions · 21 stateful · 2026-06-10 16:43:24 UTC
Parallelism
73/100
Blocked
57%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #80,401,209 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w59w010w112w013w116w219w120w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0xaef51668…083d
0x065c9d…c394
7 touches
6 conflicts
0x2df6293e…452d
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x580c6fe7…0fe4
0x1b6862…e19c
6 touches
3 conflicts
0xd5dbfacf…c5ec
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0013
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
6 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity