pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#71,045,256
← previous block
next block →
recent activity
Analyzing
Block #71,045,256
10 transactions · 10 stateful · 2026-04-28 08:34:07 UTC
Parallelism
70
/100
Blocked
30
%
Avg conflicts / tx
0.4
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,045,256
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x69f07176
#2
0x98717539
· blocks 1
#3
updatePriceFeedsIfNecessary
#4
updateDataFeedsValuesPartial
#5
setData
#7
updatePrices
· blocks 2
#6
execOrders
#8
updatePrices
· blocks 1
#9
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
6
w1
7
w0
8
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x8fd63a…536c
6 touches
3 conflicts
0x00000000…0001
0x8fd63a…536c
6 touches
3 conflicts
0xf3981be5…2c47
0x34b655…2a6f
4 touches
1 conflict
0x085df2c1…305a
0x34b655…2a6f
2 touches
0 conflicts
0x0d3d3160…bb17
0x34b655…2a6f
2 touches
0 conflicts
0x2734e46d…e50d
0x34b655…2a6f
2 touches
0 conflicts
0x3254d19b…f714
0x34b655…2a6f
2 touches
0 conflicts
0x60f7fbaf…bd58
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:
0x8fd63afb…2f536c
3 conflicts on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity