← previous blocknext block →recent activity
Analyzing
Block #80,790,593
31 transactions · 25 stateful · 2026-06-12 12:00:12 UTC
Parallelism
81/100
Blocked
60%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #80,790,593 · 31 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w19w410w011w115w016w117w218w219w320w322w428w329w430w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x217bd767…b79e
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0xe483d4e3…e52d
0x1b6862…e19c
8 touches
6 conflicts
0x679705f0…4531
0x34b655…2a6f
8 touches
6 conflicts
0x6086e62f…5c6c
0xd32edf…ff58
7 touches
6 conflicts
0x6b97d650…0509
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x217bd767aa…4fb79e
Audit this contract →
← previous block·next block →recent activity