← previous blocknext block →recent activity
Analyzing
Block #80,348,444
35 transactions · 28 stateful · 2026-06-10 10:51:44 UTC
Parallelism
80/100
Blocked
50%
Avg conflicts / tx
0.97
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #80,348,444 · 35 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w49w411w213w514w515w019w626w128w229w332w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x217bd767…b79e
0x34b655…2a6f
10 touches
10 conflicts
0x8b4b0085…6ceb
0xd32edf…ff58
9 touches
10 conflicts
0x6af306bb…2e81
0x3bd359…433a
8 touches
6 conflicts
0x1c354dc0…96de
0x754704…b603
8 touches
6 conflicts
0xf91b744e…9117
0x754704…b603
8 touches
6 conflicts
0x00000000…0029
0x1b6862…e19c
6 touches
3 conflicts
0x485d2778…aa5b
0x1b6862…e19c
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity