← previous blocknext block →recent activity
Analyzing
Block #74,566,158
68 transactions · 50 stateful · 2026-05-14 15:50:19 UTC
Parallelism
71/100
Blocked
80%
Avg conflicts / tx
3.76
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #74,566,158 · 68 txs across 20 waves · depth 20
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
wave w19
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w512w119w328w632w752w853w954w1055w1156w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
32 touches
120 conflicts
0xc6417de0…2191
0xc8689a…ee79
26 touches
78 conflicts
0xacd10bf4…2244
0x34b655…2a6f
24 touches
66 conflicts
0xa91c899f…6ee3
0x34b655…2a6f
24 touches
66 conflicts
0x8db1e0f2…2fcf
0x34b655…2a6f
24 touches
66 conflicts
0x2a89b920…34e3
0xd32edf…ff58
23 touches
66 conflicts
0x9be2b99a…a959
0x34b655…2a6f
22 touches
55 conflicts
0x0711ec2d…d973
0x34b655…2a6f
22 touches
55 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
120 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity