← previous blocknext block →recent activity
Analyzing
Block #80,408,130
56 transactions · 46 stateful · 2026-06-10 17:29:28 UTC
Parallelism
68/100
Blocked
70%
Avg conflicts / tx
2.91
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #80,408,130 · 56 txs across 18 waves · depth 18
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w07w18w19w210w311w412w513w614w715w816w917w1018w1119w1220w1322w1436w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
30 touches
105 conflicts
0x8cf3d245…1d0d
0x69df8a…6292
24 touches
66 conflicts
0x40970e69…da50
0x69df8a…6292
24 touches
66 conflicts
0xb05cd4f5…73d0
0x69df8a…6292
24 touches
66 conflicts
0xdb067026…9eb8
0x69df8a…6292
24 touches
66 conflicts
0x00000000…003d
0xa6afd3…d132
24 touches
66 conflicts
0x158accef…4c74
0xa6afd3…d132
24 touches
66 conflicts
0xe41f8863…29a4
0xa6afd3…d132
24 touches
66 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
105 conflicts on slot 0x13a54fa2d3…a35ae3
Audit this contract →
← previous block·next block →recent activity