← previous blocknext block →recent activity
Analyzing
Block #76,115,173
23 transactions · 20 stateful · 2026-05-21 20:17:29 UTC
Parallelism
83/100
Blocked
40%
Avg conflicts / tx
0.65
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #76,115,173 · 23 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
5w06w18w09w113w214w015w116w219w020w121w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x388e001a…7e04
0x34b655…2a6f
6 touches
3 conflicts
0xa472d565…9fe4
0x3bd359…433a
6 touches
3 conflicts
0x90dc86dc…5a26
0xd32edf…ff58
5 touches
3 conflicts
0x313f2565…5b00
0x34b655…2a6f
4 touches
1 conflict
0x32ee90db…decc
0x34b655…2a6f
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x6d6c951c…e464
0x34b655…2a6f
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity