← previous blocknext block →recent activity
Analyzing
Block #79,241,156
28 transactions · 25 stateful · 2026-06-05 07:33:37 UTC
Parallelism
68/100
Blocked
40%
Avg conflicts / tx
0.86
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #79,241,156 · 28 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w313w414w515w616w717w819w021w122w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x9e20cccf…19cc
0xa6afd3…d132
10 touches
10 conflicts
0xfb775e39…a412
0xd32edf…ff58
9 touches
10 conflicts
0x73912233…4585
0x1b6862…e19c
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x8cf3d245…1d0d
0x69df8a…6292
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity