← previous blocknext block →recent activity
Analyzing
Block #80,266,971
13 transactions · 10 stateful · 2026-06-10 01:48:41 UTC
Parallelism
69/100
Blocked
40%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,266,971 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0xd9f1e40f…09a3
0x3bd359…433a
4 touches
1 conflict
0x01e7b865…6e6f
0x188d58…ea8e
4 touches
1 conflict
0x527f20e3…82e7
0x754704…b603
4 touches
1 conflict
0x01e7b865…6e6d
0x188d58…ea8e
4 touches
1 conflict
0x504ac60b…20a6
0x754704…b603
4 touches
1 conflict
0xd6033c02…c385
0xd32edf…ff58
3 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
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: USDC (USDC)
3 conflicts on slot 0x17606ba612…ea1b6e
Audit this contract →
← previous block·next block →recent activity