pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#71,700,889
← previous block
next block →
recent activity
Analyzing
Block #71,700,889
12 transactions · 11 stateful · 2026-05-01 09:24:15 UTC
Parallelism
83
/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,700,889
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x1094dc9f
· blocks 1
#2
updatePrices
#3
updatePriceFeedsIfNecessary
#4
0xeffdedb0
#6
forward
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
updateDataFeedsValuesPartial
#10
setData
#11
0x0c7abd22
#5
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1a50b8eb…94da
0x065c9d…c394
3 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0003
0x0594c7…a3be
2 touches
0 conflicts
0x00000000…0004
0x0594c7…a3be
2 touches
0 conflicts
0x00000000…0005
0x0594c7…a3be
2 touches
0 conflicts
0x2241f798…95a5
0x0594c7…a3be
2 touches
0 conflicts
0x2cacf5df…2418
0x0594c7…a3be
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0x1a50b8eb36…e694da
Audit this contract →
← previous block
·
next block →
recent activity