← previous blocknext block →recent activity
Analyzing
Block #80,651,916
70 transactions · 47 stateful · 2026-06-11 20:35:41 UTC
Parallelism
77/100
Blocked
77%
Avg conflicts / tx
2.04
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #80,651,916 · 70 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w18w011w113w215w216w017w118w219w320w421w522w623w758w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
18 touches
36 conflicts
0x90f07a4f…d932
0x34b655…2a6f
18 touches
36 conflicts
0x00000000…003d
0xa6afd3…d132
16 touches
28 conflicts
0x8b3263d0…5034
0x34b655…2a6f
14 touches
21 conflicts
0x2e4eea52…0c68
0xc8689a…ee79
14 touches
21 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
14 touches
21 conflicts
0x1504aa7b…24ad
0xa6afd3…d132
14 touches
21 conflicts
0xdf708ee7…1fcf
0xc8689a…ee79
14 touches
21 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
36 conflicts on slot 0x13a54fa2d3…a35ae3
Audit this contract →
← previous block·next block →recent activity