← previous blocknext block →recent activity
Analyzing
Block #80,256,632
20 transactions · 18 stateful · 2026-06-10 00:39:42 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,256,632 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w06w17w19w012w213w316w017w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x61804e88…5a47
0xd32edf…ff58
5 touches
3 conflicts
0x21898044…a071
0x065c9d…c394
4 touches
1 conflict
0x92d610a6…9a40
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xa0f5612a…9804
0x34b655…2a6f
4 touches
1 conflict
0xa9d7cd60…1ef3
0x34b655…2a6f
4 touches
1 conflict
0x179fe783…6945
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: Perpl
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity