← previous blocknext block →recent activity
Analyzing
Block #80,408,131
50 transactions · 39 stateful · 2026-06-10 17:29:28 UTC
Parallelism
76/100
Blocked
59%
Avg conflicts / tx
1.7
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #80,408,131 · 50 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w06w39w110w211w312w413w514w615w716w819w920w1036w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
20 touches
45 conflicts
0xe41f8863…29a4
0xa6afd3…d132
18 touches
36 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
18 touches
36 conflicts
0x158accef…4c74
0xa6afd3…d132
16 touches
28 conflicts
0xdf708ee7…1fcf
0xc8689a…ee79
14 touches
21 conflicts
0xdb067026…9eb8
0x69df8a…6292
14 touches
21 conflicts
0x40970e69…da50
0x69df8a…6292
14 touches
21 conflicts
0xb05cd4f5…73d0
0x69df8a…6292
14 touches
21 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
45 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity