← previous blocknext block →recent activity
Analyzing
Block #79,418,513
20 transactions · 16 stateful · 2026-06-06 03:19:55 UTC
Parallelism
75/100
Blocked
38%
Avg conflicts / tx
0.55
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #79,418,513 · 20 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
1w02w14w05w26w37w08w113w214w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc05b880b…7746
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xa0cc5762…37dc
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0x91945265…e592
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
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
3 conflicts on slot 0xc05b880b59…957746
Audit this contract →
← previous block·next block →recent activity