← previous blocknext block →recent activity
Analyzing
Block #79,413,819
18 transactions · 15 stateful · 2026-06-06 02:48:38 UTC
Parallelism
83/100
Blocked
13%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #79,413,819 · 18 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
2w03w04w06w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7c5260f4…bd96
0xa6afd3…d132
6 touches
3 conflicts
0x2d5c395b…6b5a
0xa6afd3…d132
4 touches
1 conflict
0xef65bff3…7c9d
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xa2420403…81f8
0xa6afd3…d132
3 touches
1 conflict
0x33b3234a…bf2e
0x754704…b603
2 touches
0 conflicts
0x7e8e5d7c…0cc0
0x754704…b603
2 touches
0 conflicts
0xa1087a5c…66c4
0x754704…b603
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
3 conflicts on slot 0x7c5260f47a…bbbd96
Audit this contract →
← previous block·next block →recent activity