pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,774,641
51 transactions · 40 stateful · 2026-05-15 15:03:07 UTC
Parallelism
76/100
Blocked
73%
Avg conflicts / tx
2.27
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #74,774,641 · 51 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
1w02w13w24w06w27w39w110w011w112w213w314w415w516w617w718w823w233w437w438w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
24 touches
66 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x388e001a…7e04
0x34b655…2a6f
8 touches
6 conflicts
0xba38536d…2b7d
0x065c9d…c394
8 touches
6 conflicts
0x161e1ca1…0fd7
0x34b655…2a6f
8 touches
6 conflicts
0x3e49348b…9445
0x34b655…2a6f
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: 0xab35264b…1cfa38
66 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity