← previous blocknext block →recent activity
Analyzing
Block #80,330,090
25 transactions · 17 stateful · 2026-06-10 08:49:27 UTC
Parallelism
80/100
Blocked
47%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,330,090 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w311w412w013w114w215w322w024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa743c8dd…ebf2
0x788571…8888
8 touches
6 conflicts
0x7b9a42f7…7b88
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…0001
0x24b18e…3301
8 touches
6 conflicts
0x00000000…0000
0x24b18e…3301
8 touches
6 conflicts
0x771a3650…01cd
0x3bd359…433a
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xdb067026…9eb8
0x69df8a…6292
6 touches
3 conflicts
0x797464db…e15a
0x788571…8888
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: 0x788571e0…f48888
6 conflicts on slot 0xa743c8dd91…28ebf2
Audit this contract →
← previous block·next block →recent activity