← previous blocknext block →recent activity
Analyzing
Block #80,825,807
35 transactions · 23 stateful · 2026-06-12 15:55:00 UTC
Parallelism
86/100
Blocked
35%
Avg conflicts / tx
0.34
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,825,807 · 35 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w15w06w17w28w314w322w024w425w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x76d1e78d…7877
0x40c49f…2af0
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0xae5e6f9a…2991
0xc8689a…ee79
4 touches
1 conflict
0x5581d709…ab77
0x2a68ba…90c5
4 touches
1 conflict
0x3b9bb58c…e73a
0x34b655…2a6f
4 touches
1 conflict
0xb0e9898d…42c2
0xa6afd3…d132
4 touches
1 conflict
0xde6b917f…3a72
0xa6afd3…d132
4 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: 0x40c49f17…d22af0
6 conflicts on slot 0x76d1e78d12…117877
Audit this contract →
← previous block·next block →recent activity