pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,647,213
63 transactions · 47 stateful · 2026-05-15 00:52:02 UTC
Parallelism
81/100
Blocked
77%
Avg conflicts / tx
2.17
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #74,647,213 · 63 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
1w02w13w14w27w08w210w215w317w418w319w320w521w139w340w442w643w762w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x09dce89f…a182
0xd32edf…ff58
15 touches
28 conflicts
0x17606ba6…1b6e
0x754704…b603
14 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0x91ecc547…33f2
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…002f
0x1b6862…e19c
10 touches
10 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
36 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity