← previous blocknext block →recent activity
Analyzing
Block #79,422,827
34 transactions · 27 stateful · 2026-06-06 03:48:44 UTC
Parallelism
68/100
Blocked
48%
Avg conflicts / tx
1.91
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #79,422,827 · 34 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w17w08w09w110w211w312w413w514w615w716w818w419w920w1024w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
20 touches
45 conflicts
0x975680c7…0e39
0xa6afd3…d132
18 touches
36 conflicts
0x3287e4ec…eaa3
0xa6afd3…d132
16 touches
28 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
16 touches
28 conflicts
0xb05cd4f5…73d0
0x69df8a…6292
16 touches
28 conflicts
0xdb067026…9eb8
0x69df8a…6292
16 touches
28 conflicts
0xdf708ee7…1fcf
0xc8689a…ee79
16 touches
28 conflicts
0x40970e69…da50
0x69df8a…6292
16 touches
28 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