← previous blocknext block →recent activity
Analyzing
Block #76,031,304
13 transactions · 12 stateful · 2026-05-21 10:58:13 UTC
Parallelism
69/100
Blocked
42%
Avg conflicts / tx
0.62
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #76,031,304 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w39w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x52c63247…ce02
0x0a3323…0a3c
8 touches
6 conflicts
0x446f2734…8b54
0x0a3323…0a3c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x14d1bf0e…e09c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
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: 0x0a332311…6e0a3c
6 conflicts on slot 0x52c63247e1…bace02
Audit this contract →
← previous block·next block →recent activity