← previous blocknext block →recent activity
Analyzing
Block #80,251,017
18 transactions · 14 stateful · 2026-06-10 00:02:17 UTC
Parallelism
67/100
Blocked
50%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #80,251,017 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w37w48w59w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9f4e12e3…21c7
0x336ed4…c59c
12 touches
15 conflicts
0x00000000…000a
0x90c374…be45
12 touches
15 conflicts
0x00000000…000b
0x90c374…be45
12 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x80afd9d9…57cf
0x065c9d…c394
4 touches
1 conflict
0x6d383d1f…a65e
0x2a68ba…90c5
2 touches
1 conflict
0x1ea0a6bc…6a74
0x2a68ba…90c5
2 touches
0 conflicts
0x00000000…0004
0x546d22…8146
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: 0x336ed437…cfc59c
15 conflicts on slot 0x9f4e12e393…0a21c7
Audit this contract →
← previous block·next block →recent activity