← previous blocknext block →recent activity
Analyzing
Block #76,090,699
32 transactions · 23 stateful · 2026-05-21 17:34:26 UTC
Parallelism
78/100
Blocked
52%
Avg conflicts / tx
0.88
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #76,090,699 · 32 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w19w010w111w012w113w214w315w416w517w621w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
14 touches
21 conflicts
0xc6417de0…2191
0xc8689a…ee79
10 touches
10 conflicts
0x388e001a…7e04
0x34b655…2a6f
10 touches
10 conflicts
0x57de3828…3fbb
0x34b655…2a6f
10 touches
10 conflicts
0x908d4442…2c4b
0x34b655…2a6f
10 touches
10 conflicts
0x99f080dc…58c1
0x34b655…2a6f
10 touches
10 conflicts
0xbafe2b72…c80d
0x34b655…2a6f
10 touches
10 conflicts
0xedb848fe…6534
0x34b655…2a6f
10 touches
10 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
21 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity