← previous blocknext block →recent activity
Analyzing
Block #80,156,776
72 transactions · 57 stateful · 2026-06-09 13:33:43 UTC
Parallelism
71/100
Blocked
72%
Avg conflicts / tx
3.46
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #80,156,776 · 72 txs across 21 waves · depth 21
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
wave w17
wave w18
wave w19
wave w20
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w47w18w218w219w320w423w624w725w846w947w1048w1149w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x90f07a4f…d932
0x34b655…2a6f
24 touches
66 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
24 touches
66 conflicts
0x6ef86ae2…9baf
0xd32edf…ff58
23 touches
66 conflicts
0x00000000…001e
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…002e
0x1b6862…e19c
16 touches
28 conflicts
0x48a29a03…c43b
0x1b6862…e19c
16 touches
28 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0015
0x1b6862…e19c
16 touches
28 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 0x90f07a4ff9…b3d932
Audit this contract →
← previous block·next block →recent activity