← previous blocknext block →recent activity
Analyzing
Block #80,278,286
10 transactions · 9 stateful · 2026-06-10 03:04:06 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,278,286 · 10 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
1w02w15w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb4e0a934…5fc7
0x34b655…2a6f
4 touches
1 conflict
0x71cd8197…b6d4
0xd32edf…ff58
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x01437dd6…b014
0x065c9d…c394
2 touches
0 conflicts
0x1af204be…7de0
0x065c9d…c394
2 touches
0 conflicts
0x28f0fb54…4f36
0x065c9d…c394
2 touches
0 conflicts
0x5d1e7886…a232
0x065c9d…c394
2 touches
0 conflicts
0x80afd9d9…57cf
0x065c9d…c394
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: Perpl
1 conflict on slot 0xb4e0a934b9…435fc7
Audit this contract →
← previous block·next block →recent activity