← previous blocknext block →recent activity
Analyzing
Block #80,826,624
22 transactions · 16 stateful · 2026-06-12 16:00:29 UTC
Parallelism
86/100
Blocked
38%
Avg conflicts / tx
0.32
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,826,624 · 22 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
1w02w03w04w18w013w116w219w120w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x217bd767…b79e
0x34b655…2a6f
6 touches
3 conflicts
0x565818b0…80a3
0xa6afd3…d132
4 touches
1 conflict
0x80afd9d9…57cf
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x28a74b74…a8a3
0x34b655…2a6f
4 touches
1 conflict
0x9966da31…0d0f
0x34b655…2a6f
4 touches
1 conflict
0xa6c3f6bf…7fac
0x34b655…2a6f
4 touches
1 conflict
0xc68257b6…dd81
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
3 conflicts on slot 0x217bd767aa…4fb79e
Audit this contract →
← previous block·next block →recent activity