← previous blocknext block →recent activity
Analyzing
Block #80,448,805
45 transactions · 39 stateful · 2026-06-10 22:00:27 UTC
Parallelism
73/100
Blocked
69%
Avg conflicts / tx
2.2
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #80,448,805 · 45 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w15w06w19w210w011w112w213w314w415w516w617w718w833w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
16 touches
28 conflicts
0xdc120748…ff36
0xa6afd3…d132
16 touches
28 conflicts
0xdf708ee7…1fcf
0xc8689a…ee79
14 touches
21 conflicts
0xef65bff3…7c9d
0x2a68ba…90c5
14 touches
21 conflicts
0xb05cd4f5…73d0
0x69df8a…6292
14 touches
21 conflicts
0xdb067026…9eb8
0x69df8a…6292
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: 0xa6afd386…b0d132
28 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity