pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#71,172,381
← previous block
next block →
recent activity
Analyzing
Block #71,172,381
10 transactions · 9 stateful · 2026-04-28 22:40:52 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,172,381
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
artefact_keep
#3
setData
#4
0x6463ffd1
· blocks 1
#6
0x0c7abd22
#7
0x64480813
#8
0x39435dac
#9
updatePrices
#5
0x6463ffd1
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
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
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x44513342…6fe7
0x065c9d…c394
3 touches
1 conflict
0xc21fc26f…3dc0
0x065c9d…c394
3 touches
1 conflict
0xd63729fb…c0ec
0x065c9d…c394
3 touches
1 conflict
0x9e8f801d…a1dc
0x065c9d…c394
3 touches
1 conflict
0x5f90c0c2…8225
0x065c9d…c394
2 touches
1 conflict
0x07353542…6123
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