← previous blocknext block →recent activity
Analyzing
Block #76,465,246
29 transactions · 26 stateful · 2026-05-23 11:08:26 UTC
Parallelism
76/100
Blocked
65%
Avg conflicts / tx
1.38
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #76,465,246 · 29 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w26w37w48w59w610w111w512w013w114w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0bd261be…21c6
0xa6afd3…d132
10 touches
10 conflicts
0x99a4d286…ad43
0xa6afd3…d132
10 touches
10 conflicts
0xc3afb222…4d17
0xa6afd3…d132
10 touches
10 conflicts
0x99a21305…dffc
0x2a68ba…90c5
10 touches
10 conflicts
0xedb848fe…6534
0x34b655…2a6f
10 touches
10 conflicts
0xc6417de0…2191
0xc8689a…ee79
10 touches
10 conflicts
0x1c913164…5c2e
0x34b655…2a6f
8 touches
6 conflicts
0x493e94e2…7950
0x34b655…2a6f
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 0x0bd261be2c…3921c6
Audit this contract →
← previous block·next block →recent activity