← previous blocknext block →recent activity
Analyzing
Block #80,625,022
70 transactions · 51 stateful · 2026-06-11 17:36:18 UTC
Parallelism
76/100
Blocked
73%
Avg conflicts / tx
2.86
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #80,625,022 · 70 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
2w03w15w06w07w09w110w216w121w122w123w224w325w426w527w628w729w830w931w1032w1133w1234w1336w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
30 touches
105 conflicts
0xef65bff3…7c9d
0x2a68ba…90c5
30 touches
105 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
30 touches
105 conflicts
0xfe1362cf…bb85
0xa6afd3…d132
30 touches
105 conflicts
0xe5a10916…8ad0
0xa6afd3…d132
30 touches
105 conflicts
0xdf708ee7…1fcf
0xc8689a…ee79
28 touches
91 conflicts
0x40970e69…da50
0x69df8a…6292
28 touches
91 conflicts
0x8cf3d245…1d0d
0x69df8a…6292
28 touches
91 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: 0xa6afd386…b0d132
105 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity