← previous blocknext block →recent activity
Analyzing
Block #79,407,666
27 transactions · 25 stateful · 2026-06-06 02:07:35 UTC
Parallelism
74/100
Blocked
48%
Avg conflicts / tx
1.26
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #79,407,666 · 27 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w15w26w37w48w49w510w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5df6102c…6494
0xa6afd3…d132
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x9ff176a9…152e
0x065c9d…c394
8 touches
6 conflicts
0x7b7af531…48f1
0xa6afd3…d132
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x40970e69…da50
0x69df8a…6292
4 touches
1 conflict
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
10 conflicts on slot 0x5df6102cfc…c86494
Audit this contract →
← previous block·next block →recent activity