pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #75,478,621
47 transactions · 28 stateful · 2026-05-18 21:25:46 UTC
Parallelism
64/100
Blocked
71%
Avg conflicts / tx
2.98
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #75,478,621 · 47 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w911w1019w124w1125w1228w1329w1430w1531w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00b1a20c…b317
0xd32edf…ff58
33 touches
136 conflicts
0x22e0cc1d…ad04
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe5e7089a…fb91
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x6af306bb…2e81
0x3bd359…433a
4 touches
1 conflict
0xce8bbe33…b72e
0x3bd359…433a
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: 0xd32edf66…9fff58
136 conflicts on slot 0x00b1a20c99…11b317
Audit this contract →
← previous block·next block →recent activity