← previous blocknext block →recent activity
Analyzing
Block #80,630,968
87 transactions · 64 stateful · 2026-06-11 18:15:58 UTC
Parallelism
80/100
Blocked
77%
Avg conflicts / tx
3.32
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #80,630,968 · 87 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
1w02w13w24w35w46w57w219w321w422w523w631w1132w1233w1339w1442w1554w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
24 touches
66 conflicts
0x5c71bc6c…b0eb
0xd32edf…ff58
23 touches
66 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
20 touches
45 conflicts
0x90f07a4f…d932
0x34b655…2a6f
16 touches
28 conflicts
0x00000000…003d
0xa6afd3…d132
16 touches
28 conflicts
0x936f37a8…9812
0xa6afd3…d132
16 touches
28 conflicts
0xef65bff3…7c9d
0x2a68ba…90c5
16 touches
28 conflicts
0x00000000…0013
0x1b6862…e19c
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: Perpl
66 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity