pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#71,648,279
← previous block
next block →
recent activity
Analyzing
Block #71,648,279
10 transactions · 9 stateful · 2026-05-01 03:33:58 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,648,279
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
execute
#3
0xeffdedb0
#4
updateDataFeedsValuesPartial
#5
setData
#6
0x6df9e92b
· blocks 1
#8
0x69f41f9e
#9
modifyLiquidities
#7
0x6df9e92b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaa3e5ab2…fd8a
0x3bd359…433a
4 touches
1 conflict
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0x44ad89ba…cf83
0x7131ec…7777
4 touches
1 conflict
0x00000000…0000
0xc82b5c…bb3a
4 touches
1 conflict
0x00000000…0001
0xc82b5c…bb3a
4 touches
1 conflict
0xd46cd782…e7f2
0x7131ec…7777
4 touches
1 conflict
0x01e7b865…6e6d
0x188d58…ea8e
2 touches
0 conflicts
0x01e7b865…6e6f
0x188d58…ea8e
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:
0x3bd359c1…15433a
1 conflict on slot
0xaa3e5ab2a1…b6fd8a
Audit this contract →
← previous block
·
next block →
recent activity