← previous blocknext block →recent activity
Analyzing
Block #76,090,049
32 transactions · 29 stateful · 2026-05-21 17:30:04 UTC
Parallelism
69/100
Blocked
79%
Avg conflicts / tx
2.72
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #76,090,049 · 32 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w59w610w411w626w627w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
20 touches
45 conflicts
0xe9141f59…9f99
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…0013
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…001c
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…002c
0x1b6862…e19c
14 touches
21 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
14 touches
21 conflicts
0x3293a887…4401
0x1b6862…e19c
14 touches
21 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
45 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity