← previous blocknext block →recent activity
Analyzing
Block #76,495,855
18 transactions · 16 stateful · 2026-05-23 14:32:24 UTC
Parallelism
61/100
Blocked
56%
Avg conflicts / tx
1.17
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #76,495,855 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w25w36w47w08w19w010w511w512w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb5ff57d6…7f4c
0xa6afd3…d132
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001c
0x1b6862…e19c
8 touches
6 conflicts
0x6293451d…dcb1
0xa6afd3…d132
8 touches
6 conflicts
0x0a85a226…83be
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 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: 0xa6afd386…b0d132
10 conflicts on slot 0xb5ff57d6fb…867f4c
Audit this contract →
← previous block·next block →recent activity