pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#71,044,883
← previous block
next block →
recent activity
Analyzing
Block #71,044,883
13 transactions · 11 stateful · 2026-04-28 08:31:37 UTC
Parallelism
85
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,044,883
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
updatePrices
#3
0x98717539
· blocks 1
#4
0xed82b078
#5
updateDataFeedsValuesPartial
#6
setData
#7
0x69f070e1
#9
execOrders
#10
execOrders
#11
execOrders
#12
execOrders
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c913164…5c2e
0x34b655…2a6f
4 touches
1 conflict
0x629480fc…7d2f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x1cc5411d…dda3
0x065c9d…c394
2 touches
0 conflicts
0xd2078ebe…4eb0
0x065c9d…c394
2 touches
0 conflicts
0xdfa218b3…3bb7
0x065c9d…c394
2 touches
0 conflicts
0xf96d5064…3718
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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
0x1c913164f5…845c2e
Audit this contract →
← previous block
·
next block →
recent activity