← previous blocknext block →recent activity
Analyzing
Block #80,754,102
95 transactions · 73 stateful · 2026-06-12 07:56:54 UTC
Parallelism
78/100
Blocked
79%
Avg conflicts / tx
3.06
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #80,754,102 · 95 txs across 21 waves · depth 21
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
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
wave w19
wave w20
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w27w38w012w113w014w415w416w119w524w443w144w145w658w259w360w466w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
32 touches
120 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
18 touches
36 conflicts
0x9a76a454…14e4
0xd32edf…ff58
17 touches
36 conflicts
0x17606ba6…1b6e
0x754704…b603
12 touches
15 conflicts
0x00000000…003d
0xa6afd3…d132
12 touches
15 conflicts
0x565818b0…80a3
0xa6afd3…d132
12 touches
15 conflicts
0x9e20cccf…19cc
0xa6afd3…d132
12 touches
15 conflicts
0x90f07a4f…d932
0x34b655…2a6f
12 touches
15 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
120 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity