← previous blocknext block →recent activity
Analyzing
Block #80,826,631
31 transactions · 21 stateful · 2026-06-12 16:00:32 UTC
Parallelism
90/100
Blocked
38%
Avg conflicts / tx
0.32
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,826,631 · 31 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
1w02w13w28w19w211w014w119w020w123w025w127w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7cb2f3fa…4836
0x34b655…2a6f
6 touches
3 conflicts
0xd7df7783…ccfd
0x34b655…2a6f
6 touches
3 conflicts
0x90f07a4f…d932
0x34b655…2a6f
6 touches
3 conflicts
0x42e68c86…efea
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0x44d7acbf…e67d
0x1b6862…e19c
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: Perpl
3 conflicts on slot 0x7cb2f3fa36…384836
Audit this contract →
← previous block·next block →recent activity