pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#71,244,209
← previous block
next block →
recent activity
Analyzing
Block #71,244,209
13 transactions · 12 stateful · 2026-04-29 06:38:40 UTC
Parallelism
85
/100
Blocked
17
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,244,209
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x98717539
· blocks 1
#2
0x0c7abd22
#3
0x0c7abd22
#4
0x6463ffd1
· blocks 1
#6
forward
#7
forward
#8
updateDataFeedsValuesPartial
#9
0x69f1a7e7
#10
approve
#11
setData
#5
0x6463ffd1
#12
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w0
5
w1
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaa3492db…3703
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x1be681c7…a3cb
0x065c9d…c394
4 touches
1 conflict
0xc6cb1653…cb71
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
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:
0x34b6552d…112a6f
1 conflict on slot
0xaa3492db13…fc3703
Audit this contract →
← previous block
·
next block →
recent activity