← previous blocknext block →recent activity
Analyzing
Block #76,033,904
34 transactions · 30 stateful · 2026-05-21 11:15:32 UTC
Parallelism
82/100
Blocked
57%
Avg conflicts / tx
1.18
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #76,033,904 · 34 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w312w413w414w415w416w017w418w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
12 touches
15 conflicts
0x2e58ffb3…54d0
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…001b
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002b
0x1b6862…e19c
6 touches
3 conflicts
0x872e51c8…ae28
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x6af306bb…2e81
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 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: 0xab35264b…1cfa38
15 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity