← previous blocknext block →recent activity
Analyzing
Block #79,115,044
25 transactions · 23 stateful · 2026-06-04 17:32:45 UTC
Parallelism
68/100
Blocked
43%
Avg conflicts / tx
1.28
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #79,115,044 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w36w47w58w613w414w516w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb68e226d…c054
0xa6afd3…d132
12 touches
15 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
12 touches
15 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0xca0f0668…caf3
0xa6afd3…d132
10 touches
10 conflicts
0xdb067026…9eb8
0x69df8a…6292
8 touches
6 conflicts
0xdf708ee7…1fcf
0xc8689a…ee79
8 touches
6 conflicts
0x40970e69…da50
0x69df8a…6292
8 touches
6 conflicts
0x8cf3d245…1d0d
0x69df8a…6292
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
15 conflicts on slot 0xb68e226d12…aac054
Audit this contract →
← previous block·next block →recent activity