pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#71,683,604
← previous block
next block →
recent activity
Analyzing
Block #71,683,604
13 transactions · 9 stateful · 2026-05-01 07:29:11 UTC
Parallelism
77
/100
Blocked
22
%
Avg conflicts / tx
0.23
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,683,604
· 13 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 2
#3
0xe0de3ed7
#4
updateDataFeedsValuesPartial
#5
0xeffdedb0
#6
0x3f5c179b
#7
0x0f6795d9
#8
0x0f6795d9
#9
setData
#10
0x61633731
#11
get
#2
0x0c7abd22
· blocks 1
#12
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
12
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc52cacdf…ed23
0xd32edf…ff58
5 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x2a973536…afc1
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001c
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:
0xd32edf66…9fff58
3 conflicts on slot
0xc52cacdffe…b5ed23
Audit this contract →
← previous block
·
next block →
recent activity