← previous blocknext block →recent activity
Analyzing
Block #79,407,544
45 transactions · 40 stateful · 2026-06-06 02:06:46 UTC
Parallelism
53/100
Blocked
78%
Avg conflicts / tx
4.36
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #79,407,544 · 45 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
1w02w13w24w15w07w110w311w312w420w1121w1222w1328w1929w2034w1435w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
32 touches
120 conflicts
0x5df6102c…6494
0xa6afd3…d132
30 touches
105 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
30 touches
105 conflicts
0x7b7af531…48f1
0xa6afd3…d132
30 touches
105 conflicts
0xdb067026…9eb8
0x69df8a…6292
28 touches
91 conflicts
0xdf708ee7…1fcf
0xc8689a…ee79
28 touches
91 conflicts
0x40970e69…da50
0x69df8a…6292
28 touches
91 conflicts
0xb05cd4f5…73d0
0x69df8a…6292
28 touches
91 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
120 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity