← previous blocknext block →recent activity
Analyzing
Block #80,165,141
41 transactions · 32 stateful · 2026-06-09 14:29:33 UTC
Parallelism
81/100
Blocked
50%
Avg conflicts / tx
1.63
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #80,165,141 · 41 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
1w02w13w24w35w49w414w015w116w218w519w634w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x8bd75c64…7597
0xd32edf…ff58
13 touches
21 conflicts
0xcb89a818…e7c1
0x34b655…2a6f
10 touches
10 conflicts
0xe1791476…927a
0x34b655…2a6f
9 touches
13 conflicts
0x00000000…002e
0x1b6862…e19c
8 touches
6 conflicts
0x3af0dd8e…0027
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x0462262d…a368
0x34b655…2a6f
8 touches
6 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
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity