← previous blocknext block →recent activity
Analyzing
Block #80,256,388
45 transactions · 38 stateful · 2026-06-10 00:38:04 UTC
Parallelism
71/100
Blocked
68%
Avg conflicts / tx
2.16
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #80,256,388 · 45 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w17w08w19w210w311w412w513w628w729w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x3c7520fc…9ca3
0x34b655…2a6f
10 touches
10 conflicts
0x179fe783…6945
0xa6afd3…d132
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x90f07a4f…d932
0x34b655…2a6f
10 touches
10 conflicts
0x40970e69…da50
0x69df8a…6292
8 touches
6 conflicts
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
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity