← previous blocknext block →recent activity
Analyzing
Block #76,148,929
22 transactions · 18 stateful · 2026-05-22 00:02:19 UTC
Parallelism
86/100
Blocked
44%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #76,148,929 · 22 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w18w210w011w112w213w014w015w116w220w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
6 touches
3 conflicts
0xfe2bac2b…2cec
0x065c9d…c394
6 touches
3 conflicts
0xa472d565…9fe4
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x697fb4a8…ffac
0x065c9d…c394
4 touches
1 conflict
0xbce67a96…ad00
0x065c9d…c394
4 touches
1 conflict
0x00000000…0000
0x30611e…d8d9
4 touches
1 conflict
0x00000000…0002
0x30611e…d8d9
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
3 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity