← previous blocknext block →recent activity
Analyzing
Block #80,163,898
54 transactions · 44 stateful · 2026-06-09 14:21:15 UTC
Parallelism
69/100
Blocked
75%
Avg conflicts / tx
4.17
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #80,163,898 · 54 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w17w211w012w113w214w315w416w517w618w719w820w921w1022w1123w1224w1325w1426w1527w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
34 touches
136 conflicts
0x00000000…003d
0xa6afd3…d132
30 touches
105 conflicts
0xdf708ee7…1fcf
0xc8689a…ee79
28 touches
91 conflicts
0x8cf3d245…1d0d
0x69df8a…6292
26 touches
78 conflicts
0x36d366fe…7adc
0xa6afd3…d132
26 touches
78 conflicts
0x40970e69…da50
0x69df8a…6292
26 touches
78 conflicts
0x7531e9d9…196d
0xa6afd3…d132
24 touches
66 conflicts
0xdb067026…9eb8
0x69df8a…6292
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
136 conflicts on slot 0x13a54fa2d3…a35ae3
Audit this contract →
← previous block·next block →recent activity