← previous blocknext block →recent activity
Analyzing
Block #79,250,090
25 transactions · 18 stateful · 2026-06-05 08:33:20 UTC
Parallelism
80/100
Blocked
44%
Avg conflicts / tx
0.72
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #79,250,090 · 25 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
2w03w04w15w26w37w09w111w412w015w120w021w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xde6b917f…3a72
0xa6afd3…d132
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0xb0e9898d…42c2
0xa6afd3…d132
10 touches
10 conflicts
0x40970e69…da50
0x69df8a…6292
8 touches
6 conflicts
0x8cf3d245…1d0d
0x69df8a…6292
8 touches
6 conflicts
0xb05cd4f5…73d0
0x69df8a…6292
8 touches
6 conflicts
0xdb067026…9eb8
0x69df8a…6292
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 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
10 conflicts on slot 0xde6b917faa…a83a72
Audit this contract →
← previous block·next block →recent activity