pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#71,688,572
← previous block
next block →
recent activity
Analyzing
Block #71,688,572
10 transactions · 9 stateful · 2026-05-01 08:02:13 UTC
Parallelism
60
/100
Blocked
33
%
Avg conflicts / tx
0.6
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,688,572
· 10 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
0x0c7abd22
· blocks 3
#2
0x76368669
#5
updateDataFeedsValuesPartial
#6
0xeffdedb0
#8
0x3f5c179b
#9
setData
#3
0x0c7abd22
· blocks 2
#4
0x0c7abd22
· blocks 1
#7
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
4
w2
7
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe9022c29…b7ce
0xd32edf…ff58
7 touches
6 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
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
0x00000000…002c
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
6 conflicts on slot
0xe9022c298c…e2b7ce
Audit this contract →
← previous block
·
next block →
recent activity