pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#70,891,518
← previous block
next block →
recent activity
Analyzing
Block #70,891,518
12 transactions · 11 stateful · 2026-04-27 15:30:24 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,891,518
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x5bf9264c
#3
0x98717539
#4
updateDataFeedsValuesPartial
#5
0xd2952904
#6
forward
#7
forward
#8
commit
#9
setData
#10
updatePrices
· blocks 1
#11
updatePrices
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0001
0xc1a578…8e1a
4 touches
1 conflict
0x00000000…0000
0xc1a578…8e1a
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x51087f5a…61f7
0x34b655…2a6f
2 touches
0 conflicts
0x544745e8…d72e
0x34b655…2a6f
2 touches
0 conflicts
0x76da8d77…bc80
0x34b655…2a6f
2 touches
0 conflicts
0xa7ecbbe7…f713
0x34b655…2a6f
2 touches
0 conflicts
0xd3f6a188…324f
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:
0xc1a5781e…c78e1a
1 conflict on slot
0x0000000000…000001
Audit this contract →
← previous block
·
next block →
recent activity