← previous blocknext block →recent activity
Analyzing
Block #80,465,144
29 transactions · 23 stateful · 2026-06-10 23:49:23 UTC
Parallelism
83/100
Blocked
48%
Avg conflicts / tx
0.66
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,465,144 · 29 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
1w02w13w24w313w014w116w017w118w219w020w121w222w126w327w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c7763f6…89be
0x34b655…2a6f
8 touches
6 conflicts
0x4064c9fc…902b
0xd32edf…ff58
7 touches
6 conflicts
0x90f07a4f…d932
0x34b655…2a6f
6 touches
3 conflicts
0xc38151f2…2bcb
0xc8689a…ee79
6 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c3
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x2f0eb37d…db5b
0x34b655…2a6f
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
6 conflicts on slot 0x1c7763f6c9…dd89be
Audit this contract →
← previous block·next block →recent activity