pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#71,094,743
← previous block
next block →
recent activity
Analyzing
Block #71,094,743
15 transactions · 12 stateful · 2026-04-28 14:03:47 UTC
Parallelism
87
/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,094,743
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
· blocks 1
#3
0x69f0beba
#4
0x1a945f9c
#5
0x98717539
#6
0x98717539
#7
0xc0acd4…2b1a
#8
updateDataFeedsValuesPartial
#9
0x6463ffd1
#10
forward
#11
forward
#12
0x6df9e92b
#13
setData
#14
execute
#2
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xb857c1…9be1
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
0x0d622e34…0000
0x681e90…ae09
2 touches
0 conflicts
0x00000000…006f
0x1efe02…37d6
2 touches
0 conflicts
0x021ab6f5…4fc7
0x1efe02…37d6
2 touches
0 conflicts
0x1c28e67a…9b1a
0x1efe02…37d6
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