← previous blocknext block →recent activity
Analyzing
Block #80,266,125
34 transactions · 29 stateful · 2026-06-10 01:43:03 UTC
Parallelism
76/100
Blocked
62%
Avg conflicts / tx
1.79
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #80,266,125 · 34 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w08w29w310w411w512w627w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x90f07a4f…d932
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…003d
0xa6afd3…d132
12 touches
15 conflicts
0x179fe783…6945
0xa6afd3…d132
12 touches
15 conflicts
0xa973fa68…f94d
0xa6afd3…d132
12 touches
15 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
12 touches
15 conflicts
0x083a8763…5a78
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0xef65bff3…7c9d
0x2a68ba…90c5
10 touches
10 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
21 conflicts on slot 0x90f07a4ff9…b3d932
Audit this contract →
← previous block·next block →recent activity