pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,516,429
170 transactions · 38 stateful · 2026-05-14 10:14:46 UTC
Parallelism
90/100
Blocked
79%
Avg conflicts / tx
1.14
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #74,516,429 · 170 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
49w052w154w256w358w460w562w664w767w871w975w1079w1182w1285w1388w14160w15164w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…641c
0x34b655…2a6f
34 touches
136 conflicts
0xea02471d…1539
0x34b655…2a6f
18 touches
36 conflicts
0xf853eb8e…401e
0x34b655…2a6f
18 touches
36 conflicts
0x22e0cc1d…ad04
0x34b655…2a6f
14 touches
21 conflicts
0xac2a0273…7212
0x34b655…2a6f
14 touches
21 conflicts
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x00000000…0002
0xab3526…fa38
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 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: 0x34b6552d…112a6f
136 conflicts on slot 0xc824469a90…af641c
Audit this contract →
← previous block·next block →recent activity