pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,420,886
56 transactions · 33 stateful · 2026-05-13 23:37:36 UTC
Parallelism
79/100
Blocked
73%
Avg conflicts / tx
1.64
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #74,420,886 · 56 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w47w58w69w714w217w620w426w729w544w845w946w1053w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d98876f…0063
0xd32edf…ff58
23 touches
66 conflicts
0x00000000…0002
0xab3526…fa38
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001b
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002b
0x1b6862…e19c
8 touches
6 conflicts
0x3293a887…4400
0x1b6862…e19c
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: 0xd32edf66…9fff58
66 conflicts on slot 0x0d98876ffa…3c0063
Audit this contract →
← previous block·next block →recent activity