← previous blocknext block →recent activity
Analyzing
Block #80,330,445
28 transactions · 20 stateful · 2026-06-10 08:51:49 UTC
Parallelism
86/100
Blocked
45%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,330,445 · 28 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
2w03w14w27w08w19w010w213w314w015w123w124w226w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x217bd767…b79e
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x80afd9d9…57cf
0x065c9d…c394
6 touches
3 conflicts
0x8fbde2b3…9b8f
0x34b655…2a6f
6 touches
3 conflicts
0xecb4264b…7cf9
0x34b655…2a6f
6 touches
3 conflicts
0x7602f96e…cc23
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0001
0x24b18e…3301
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 0x217bd767aa…4fb79e
Audit this contract →
← previous block·next block →recent activity