← previous blocknext block →recent activity
Analyzing
Block #79,413,804
34 transactions · 29 stateful · 2026-06-06 02:48:32 UTC
Parallelism
62/100
Blocked
62%
Avg conflicts / tx
2.5
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #79,413,804 · 34 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w17w28w39w410w511w612w713w814w915w1016w1122w127w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
24 touches
66 conflicts
0xdb067026…9eb8
0x69df8a…6292
22 touches
55 conflicts
0xb05cd4f5…73d0
0x69df8a…6292
22 touches
55 conflicts
0xef65bff3…7c9d
0x2a68ba…90c5
22 touches
55 conflicts
0xdf708ee7…1fcf
0xc8689a…ee79
22 touches
55 conflicts
0x2d5c395b…6b5a
0xa6afd3…d132
20 touches
45 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
20 touches
45 conflicts
0x7c5260f4…bd96
0xa6afd3…d132
20 touches
45 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
66 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity