← previous blocknext block →recent activity
Analyzing
Block #79,418,344
16 transactions · 13 stateful · 2026-06-06 03:18:48 UTC
Parallelism
81/100
Blocked
15%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #79,418,344 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5da4ed2f…283f
0xa6afd3…d132
4 touches
1 conflict
0xc05b880b…7746
0xa6afd3…d132
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xb3572c95…9c4a
0x2a68ba…90c5
2 touches
0 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
2 touches
0 conflicts
0x00000000…003d
0x40c49f…2af0
2 touches
0 conflicts
0x296e62d0…5f40
0x40c49f…2af0
2 touches
0 conflicts
0x37b8bec2…19cc
0x40c49f…2af0
2 touches
0 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
1 conflict on slot 0x5da4ed2fdd…52283f
Audit this contract →
← previous block·next block →recent activity