← previous blocknext block →recent activity
Analyzing
Block #76,559,618
13 transactions · 11 stateful · 2026-05-23 21:37:05 UTC
Parallelism
69/100
Blocked
27%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #76,559,618 · 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
4w05w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a809ce1…7894
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x12e7c471…901c
0x34b655…2a6f
5 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x544745e8…d72e
0x34b655…2a6f
3 touches
1 conflict
0x00000000…001e
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002e
0x1b6862…e19c
2 touches
0 conflicts
0xba5743c7…21c5
0x1b6862…e19c
2 touches
0 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: Perpl
3 conflicts on slot 0x0a809ce130…5f7894
Audit this contract →
← previous block·next block →recent activity