pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,430,791
← previous block
next block →
recent activity
Analyzing
Block #74,430,791
12 transactions · 9 stateful · 2026-05-14 00:43:36 UTC
Parallelism
83
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,430,791
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updatePrices
#3
updatePrices
#4
updatePrices
#5
0x39435dac
· blocks 1
#6
0x6df9e92b
#7
forward
#8
updateDataFeedsValuesPartial
#9
approve
#10
setData
#11
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbb1747e2…f78b
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x13a25496…a86d
0x065c9d…c394
2 touches
0 conflicts
0x42ba3228…23a4
0x065c9d…c394
2 touches
0 conflicts
0x7d00decc…4043
0x065c9d…c394
2 touches
0 conflicts
0xb4bc89e8…bcbf
0x065c9d…c394
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
0xbb1747e217…82f78b
Audit this contract →
← previous block
·
next block →
recent activity