← previous blocknext block →recent activity
Analyzing
Block #80,163,321
15 transactions · 12 stateful · 2026-06-09 14:17:24 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,163,321 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w08w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0x5a9b5dbd…0afc
0xd32edf…ff58
3 touches
1 conflict
0x6d383d1f…a65e
0x2a68ba…90c5
2 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x2aa77b01…5d24
0x065c9d…c394
2 touches
0 conflicts
0x4466e8fc…ba5c
0x065c9d…c394
2 touches
0 conflicts
0x64f023cc…0e4b
0x065c9d…c394
2 touches
0 conflicts
0x67ec9496…5d66
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: 0x681e908b…e1ae09
3 conflicts on slot 0x0d622e34f9…000000
Audit this contract →
← previous block·next block →recent activity