pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,770,481
← previous block
next block →
recent activity
Analyzing
Block #74,770,481
9 transactions · 7 stateful · 2026-05-15 14:35:17 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,770,481
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6a072f9d
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
forward
#5
setData
#6
0x39435dac
· blocks 1
#8
jMMeC
#7
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4fa72287…fa62
0x34b655…2a6f
4 touches
1 conflict
0xfa2527aa…9dd5
0x34b655…2a6f
4 touches
1 conflict
0x5ffc25fa…b119
0x34b655…2a6f
4 touches
1 conflict
0xb9868b52…c77f
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xdbadf6b0…43b2
0x33176b…e078
2 touches
0 conflicts
0xe5e7089a…fb91
0x34b655…2a6f
2 touches
0 conflicts
0x0d622e34…0000
0x681e90…ae09
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:
Perpl
1 conflict on slot
0x4fa72287ab…d5fa62
Audit this contract →
← previous block
·
next block →
recent activity