← previous blocknext block →recent activity
Analyzing
Block #76,166,971
25 transactions · 21 stateful · 2026-05-22 02:02:27 UTC
Parallelism
84/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #76,166,971 · 25 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
1w02w13w04w07w18w19w010w111w019w121w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x388f889f…a655
0x34b655…2a6f
6 touches
3 conflicts
0x801a6e57…d85c
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x01e7b865…6e6e
0x188d58…ea8e
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
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: Perpl
3 conflicts on slot 0x388f889f28…0aa655
Audit this contract →
← previous block·next block →recent activity