pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#71,042,856
← previous block
next block →
recent activity
Analyzing
Block #71,042,856
14 transactions · 12 stateful · 2026-04-28 08:18:07 UTC
Parallelism
86
/100
Blocked
8
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,042,856
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x4500f50f
#2
trade
#3
updatePrices
· blocks 1
#5
updatePrices
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
0x98717539
#9
artefact_keep
#10
setData
#11
0x0c7abd22
#12
updatePrices
#13
updatePrices
#4
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xb857c1…9be1
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0e891d1a…68c4
0x065c9d…c394
2 touches
0 conflicts
0x1ecee167…9364
0x188d58…ea8e
2 touches
0 conflicts
0x1ecee167…9366
0x188d58…ea8e
2 touches
0 conflicts
0xc3c8642a…7da5
0x2a68ba…90c5
2 touches
0 conflicts
0x2881ee90…ef2e
0x3bd359…433a
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:
0xb857c13a…1a9be1
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity