← previous blocknext block →recent activity
Analyzing
Block #80,448,785
19 transactions · 18 stateful · 2026-06-10 22:00:19 UTC
Parallelism
58/100
Blocked
44%
Avg conflicts / tx
1.53
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #80,448,785 · 19 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
16 touches
28 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
12 touches
15 conflicts
0xdc120748…ff36
0xa6afd3…d132
12 touches
15 conflicts
0xdf708ee7…1fcf
0xc8689a…ee79
12 touches
15 conflicts
0x8cf3d245…1d0d
0x69df8a…6292
10 touches
10 conflicts
0xdb067026…9eb8
0x69df8a…6292
10 touches
10 conflicts
0xef65bff3…7c9d
0x2a68ba…90c5
10 touches
10 conflicts
0x424eca3b…f2ab
0xa6afd3…d132
10 touches
10 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