pev
.
One block, wave by wave
→
analytics
docs
offline
by Silk Nodes →
pev
/
block
/
#74,289,065
← previous block
next block →
recent activity
Analyzing
Block #74,289,065
9 transactions · 7 stateful · 2026-05-13 09:00:31 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,289,065
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39435dac
· blocks 1
#2
0x6a043e27
#3
updateDataFeedsValuesPartial
#4
0x98717539
· blocks 1
#6
setData
#7
0x6a043e27
#8
handleOps
#5
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x94710b77…a921
0x34b655…2a6f
4 touches
1 conflict
0x15c9b5bf…f732
0x34b655…2a6f
4 touches
1 conflict
0xf6c9bf9b…ac02
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xafd59af5…5257
0xc8689a…ee79
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
2 touches
0 conflicts
0x7a3c0593…b564
0x34b655…2a6f
2 touches
0 conflicts
0x81220e4d…bd9c
0x34b655…2a6f
2 touches
0 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
1 conflict on slot
0x94710b77de…eca921
Audit this contract →
← previous block
·
next block →
recent activity