← previous blocknext block →recent activity
Analyzing
Block #80,251,031
23 transactions · 19 stateful · 2026-06-10 00:02:23 UTC
Parallelism
74/100
Blocked
42%
Avg conflicts / tx
0.91
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #80,251,031 · 23 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
1w02w13w04w05w06w17w28w39w410w511w012w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…000b
0x90c374…be45
12 touches
15 conflicts
0x9f4e12e3…21c7
0x336ed4…c59c
12 touches
15 conflicts
0x00000000…000a
0x90c374…be45
12 touches
15 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xb3572c95…9c4a
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x7531e9d9…196d
0xa6afd3…d132
4 touches
1 conflict
0xccd2f525…3bd4
0xd32edf…ff58
3 touches
1 conflict
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: 0x90c3747c…0ebe45
15 conflicts on slot 0x0000000000…00000b
Audit this contract →
← previous block·next block →recent activity