pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#74,902,010
← previous block
next block →
recent activity
Analyzing
Block #74,902,010
14 transactions · 10 stateful · 2026-05-16 05:12:47 UTC
Parallelism
86
/100
Blocked
10
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,902,010
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x98717539
· blocks 1
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
batchUpdate
#6
0x6a07fd47
#7
0x9d7574…65a0
#8
0xe64b68…59d7
#9
setData
#10
execOrders
#11
execOrders
#12
execOrders
#13
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
13
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa92c8763…6d7f
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
2 touches
0 conflicts
0x3c382fd1…192d
0x34b655…2a6f
2 touches
0 conflicts
0x414e9446…4b59
0x34b655…2a6f
2 touches
0 conflicts
0x4548467b…9058
0x34b655…2a6f
2 touches
0 conflicts
0x5c6af4a8…6ece
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:
Perpl
1 conflict on slot
0xa92c87634b…146d7f
Audit this contract →
← previous block
·
next block →
recent activity