← previous blocknext block →recent activity
Analyzing
Block #79,418,309
26 transactions · 21 stateful · 2026-06-06 03:18:34 UTC
Parallelism
77/100
Blocked
38%
Avg conflicts / tx
0.73
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #79,418,309 · 26 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
6w07w18w29w310w414w516w020w122w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
12 touches
15 conflicts
0xc05b880b…7746
0xa6afd3…d132
12 touches
15 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
10 touches
10 conflicts
0x40970e69…da50
0x69df8a…6292
10 touches
10 conflicts
0x8cf3d245…1d0d
0x69df8a…6292
10 touches
10 conflicts
0xb05cd4f5…73d0
0x69df8a…6292
10 touches
10 conflicts
0xdb067026…9eb8
0x69df8a…6292
10 touches
10 conflicts
0x5da4ed2f…283f
0xa6afd3…d132
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: 0xa6afd386…b0d132
15 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity