← previous blocknext block →recent activity
Analyzing
Block #76,236,743
17 transactions · 17 stateful · 2026-05-22 09:47:18 UTC
Parallelism
59/100
Blocked
41%
Avg conflicts / tx
0.94
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #76,236,743 · 17 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
1w03w04w15w26w37w112w414w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x388e001a…7e04
0x34b655…2a6f
10 touches
10 conflicts
0xc6417de0…2191
0xc8689a…ee79
8 touches
6 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0x68728b15…33fc
0x34b655…2a6f
8 touches
6 conflicts
0x8db1e0f2…2fcf
0x34b655…2a6f
8 touches
6 conflicts
0x908d4442…2c4b
0x34b655…2a6f
8 touches
6 conflicts
0x99f080dc…58c1
0x34b655…2a6f
8 touches
6 conflicts
0x9be2b99a…a959
0x34b655…2a6f
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 0x388e001a16…e57e04
Audit this contract →
← previous block·next block →recent activity