pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,462,731
41 transactions · 37 stateful · 2026-05-14 04:16:17 UTC
Parallelism
81/100
Blocked
73%
Avg conflicts / tx
1.9
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #74,462,731 · 41 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w311w312w314w415w227w428w529w640w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c389468…6b0e
0x34b655…2a6f
14 touches
21 conflicts
0x8652aeb6…370a
0xd32edf…ff58
13 touches
21 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0002
0xab3526…fa38
10 touches
10 conflicts
0x00000000…002c
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
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: 0x34b6552d…112a6f
21 conflicts on slot 0x1c38946843…a16b0e
Audit this contract →
← previous block·next block →recent activity