pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#71,421,058
← previous block
next block →
recent activity
Analyzing
Block #71,421,058
11 transactions · 10 stateful · 2026-04-30 02:17:03 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,421,058
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
approve
#2
0x98717539
· blocks 1
#4
updatePriceFeedsIfNecessary
#5
0x3f5c179b
#6
0x6df9e92b
#7
updateDataFeedsValuesPartial
#8
setData
#9
0x39435dac
#10
modifyLiquidities
#3
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x17cd1479…00bb
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1ae
0x8d66a4…3095
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
0x00ece8a1…1ae8
0x34b655…2a6f
2 touches
0 conflicts
0x10f5f4d8…572e
0x34b655…2a6f
2 touches
0 conflicts
0x17141c9e…7bea
0x34b655…2a6f
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:
0x8d66a43f…113095
1 conflict on slot
0x17cd1479c2…a700bb
Audit this contract →
← previous block
·
next block →
recent activity