pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,770,811
← previous block
next block →
recent activity
Analyzing
Block #74,770,811
12 transactions · 8 stateful · 2026-05-15 14:37:31 UTC
Parallelism
83
/100
Blocked
13
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,770,811
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x1094dc9f
#2
0xa8080e…c6ff
#3
execute
#4
0x5bf9264c
· blocks 1
#6
updateDataFeedsValuesPartial
#7
redeemDelegations
#8
0x62be7533
#9
0x6a073023
#10
setData
#11
0xa83708…e0ec
#5
0x5bf9264c
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…7212
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x335a161d…fe7f
0x000000…012a
2 touches
0 conflicts
0x78ae17f2…53be
0x000000…012a
2 touches
0 conflicts
0x00000000…0001
0x010592…1c83
2 touches
0 conflicts
0x00000000…0006
0x010592…1c83
2 touches
0 conflicts
0x03f0783d…d04f
0x010592…1c83
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
0xac2a02739b…817212
Audit this contract →
← previous block
·
next block →
recent activity