pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#71,172,105
← previous block
next block →
recent activity
Analyzing
Block #71,172,105
7 transactions · 6 stateful · 2026-04-28 22:39:01 UTC
Parallelism
71
/100
Blocked
17
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,172,105
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x6463ffd1
· blocks 1
#3
setData
#4
updatePriceFeedsIfNecessary
#6
0x69f1377d
#5
0x6463ffd1
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x3e4b02f8…bf0d
0x065c9d…c394
4 touches
1 conflict
0xb028e43a…9303
0x065c9d…c394
4 touches
1 conflict
0xcf008d94…0252
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x12ca5030…c9da
0x065c9d…c394
4 touches
1 conflict
0xec0a2a96…e3c0
0x065c9d…c394
2 touches
1 conflict
0xff8a0c83…9287
0x065c9d…c394
2 touches
1 conflict
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:
0xd0f8a642…83badc
1 conflict on slot
0x0000000000…000004
Audit this contract →
← previous block
·
next block →
recent activity