← previous blocknext block →recent activity
Analyzing
Block #76,465,288
15 transactions · 14 stateful · 2026-05-23 11:08:43 UTC
Parallelism
73/100
Blocked
29%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #76,465,288 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w38w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xc3afb222…4d17
0xa6afd3…d132
6 touches
3 conflicts
0x99a4d286…ad43
0xa6afd3…d132
6 touches
3 conflicts
0x2dc020c7…0697
0xc8689a…ee79
4 touches
1 conflict
0x10abefc9…c9bc
0x1d1325…2305
4 touches
1 conflict
0x10d80fee…dbda
0x1d1325…2305
4 touches
1 conflict
0x3484c9df…bfd5
0x1d1325…2305
4 touches
1 conflict
0xdb067026…9eb8
0x1d1325…2305
4 touches
1 conflict
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity