← previous blocknext block →recent activity
Analyzing
Block #76,090,415
34 transactions · 29 stateful · 2026-05-21 17:32:32 UTC
Parallelism
85/100
Blocked
66%
Avg conflicts / tx
1.06
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #76,090,415 · 34 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w19w110w211w212w315w416w017w118w219w320w423w431w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
10 touches
10 conflicts
0x2f810b2b…2d48
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0001
0xd57e82…8ed4
8 touches
6 conflicts
0x6ac11407…0bcc
0x3bd359…433a
8 touches
6 conflicts
0xa472d565…9fe4
0x3bd359…433a
8 touches
6 conflicts
0x44ad89ba…cf83
0xd10cf1…7777
8 touches
6 conflicts
0x5180f24b…0b96
0xd10cf1…7777
8 touches
6 conflicts
0x00000000…0000
0xd57e82…8ed4
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: Perpl
10 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity