← previous blocknext block →recent activity
Analyzing
Block #79,419,020
18 transactions · 15 stateful · 2026-06-06 03:23:17 UTC
Parallelism
72/100
Blocked
40%
Avg conflicts / tx
0.78
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #79,419,020 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w15w26w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5da4ed2f…283f
0xa6afd3…d132
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0xc05b880b…7746
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…002f
0x1b6862…e19c
6 touches
3 conflicts
0x7322fb4a…635f
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xb05cd4f5…73d0
0x69df8a…6292
6 touches
3 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
6 conflicts on slot 0x5da4ed2fdd…52283f
Audit this contract →
← previous block·next block →recent activity