← previous blocknext block →recent activity
Analyzing
Block #80,233,907
23 transactions · 18 stateful · 2026-06-09 22:08:18 UTC
Parallelism
74/100
Blocked
50%
Avg conflicts / tx
1.17
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #80,233,907 · 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
1w02w03w14w25w36w413w514w019w120w221w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0xbaff104b…3edb
0xa6afd3…d132
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x9cf5ac50…1be9
0xa6afd3…d132
8 touches
6 conflicts
0x217bd767…b79e
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0x64461c10…e86d
0x34b655…2a6f
4 touches
1 conflict
0x81e1f4e8…08d7
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: 0xa6afd386…b0d132
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity