pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,795,940
23 transactions · 20 stateful · 2026-05-15 17:25:24 UTC
Parallelism
39/100
Blocked
65%
Avg conflicts / tx
3.26
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #74,795,940 · 23 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w717w818w919w1020w1122w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x62d080e9…4a7c
0x34b655…2a6f
22 touches
55 conflicts
0x1319ae2c…7f9a
0x34b655…2a6f
16 touches
28 conflicts
0x32ee90db…decc
0x34b655…2a6f
16 touches
28 conflicts
0x0b28bf77…e53a
0x34b655…2a6f
16 touches
28 conflicts
0xac8e97a0…8426
0x34b655…2a6f
16 touches
28 conflicts
0xf853eb8e…4027
0x34b655…2a6f
16 touches
28 conflicts
0xc6417de0…2191
0xc8689a…ee79
16 touches
28 conflicts
0x3b0f5871…74dd
0x34b655…2a6f
14 touches
21 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
55 conflicts on slot 0x62d080e928…5a4a7c
Audit this contract →
← previous block·next block →recent activity