← previous blocknext block →recent activity
Analyzing
Block #76,602,902
13 transactions · 11 stateful · 2026-05-24 02:25:05 UTC
Parallelism
62/100
Blocked
55%
Avg conflicts / tx
0.92
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #76,602,902 · 13 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
1w02w13w24w05w17w311w412w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf282c2b3…28b4
0xa6afd3…d132
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x3484c9df…bfd5
0x1d1325…2305
8 touches
6 conflicts
0x8cf3d245…1d0d
0x1d1325…2305
8 touches
6 conflicts
0xdb067026…9eb8
0x1d1325…2305
8 touches
6 conflicts
0xea7ebe9d…709e
0x1d1325…2305
8 touches
6 conflicts
0x99a21305…dffc
0x2a68ba…90c5
8 touches
6 conflicts
0x10abefc9…c9bc
0x1d1325…2305
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 0xf282c2b36a…3228b4
Audit this contract →
← previous block·next block →recent activity