← previous blocknext block →recent activity
Analyzing
Block #80,278,572
18 transactions · 15 stateful · 2026-06-10 03:06:01 UTC
Parallelism
89/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,278,572 · 18 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w010w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc514f614…22e7
0x5afd3e…7620
4 touches
1 conflict
0x2ccef3ad…bed9
0x5afd3e…7620
4 touches
1 conflict
0x7be9dcb7…baef
0xd32edf…ff58
3 touches
1 conflict
0x5934f6a3…b774
0x065c9d…c394
2 touches
0 conflicts
0x046a928e…0012
0x2a68ba…90c5
2 touches
0 conflicts
0x00000000…0004
0x5afd3e…7620
2 touches
0 conflicts
0x3378e8b6…20a9
0x754704…b603
2 touches
0 conflicts
0x4039b31f…0f4a
0x754704…b603
2 touches
0 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: Liquidity Book Token (LBT)
1 conflict on slot 0xc514f6144c…6922e7
Audit this contract →
← previous block·next block →recent activity