← previous blocknext block →recent activity
Analyzing
Block #80,477,651
32 transactions · 26 stateful · 2026-06-11 01:12:42 UTC
Parallelism
81/100
Blocked
62%
Avg conflicts / tx
1.06
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #80,477,651 · 32 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w06w17w28w09w110w211w312w413w016w117w218w319w427w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
12 touches
15 conflicts
0xa973fa68…f94d
0xa6afd3…d132
12 touches
15 conflicts
0xdf708ee7…1fcf
0xc8689a…ee79
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
10 touches
10 conflicts
0x179fe783…6945
0xa6afd3…d132
10 touches
10 conflicts
0xb05cd4f5…73d0
0x69df8a…6292
10 touches
10 conflicts
0xdb067026…9eb8
0x69df8a…6292
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: 0xa6afd386…b0d132
15 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity