← previous blocknext block →recent activity
Analyzing
Block #76,246,656
17 transactions · 15 stateful · 2026-05-22 10:53:17 UTC
Parallelism
71/100
Blocked
67%
Avg conflicts / tx
1.24
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #76,246,656 · 17 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
1w02w13w24w35w06w17w28w39w410w011w315w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x348fda08…7e96
0x065c9d…c394
8 touches
6 conflicts
0x3e49348b…9445
0x34b655…2a6f
6 touches
3 conflicts
0xba38536d…2b7d
0x065c9d…c394
6 touches
3 conflicts
0xcd041b2c…d016
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0x17ca7036…1e1b
0x1b6862…e19c
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: 0xab35264b…1cfa38
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity