pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#70,998,561
← previous block
next block →
recent activity
Analyzing
Block #70,998,561
10 transactions · 7 stateful · 2026-04-28 03:23:20 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,998,561
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
withdraw
#2
0x0c7abd22
· blocks 1
#4
0x6463ffd1
#5
updateDataFeedsValuesPartial
#6
0xed82b078
#7
0xed82b078
#8
setData
#9
0x024e6a00
#3
0x0c7abd22
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
0xad092ae6…b421
0x754704…b603
4 touches
1 conflict
0xd381d0e5…7437
0x1b6862…e19c
4 touches
1 conflict
0x4d10fad4…b8e0
0x3bd359…433a
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x0e5193d1…4fdc
0xd32edf…ff58
3 touches
1 conflict
0x33018431…8f5c
0x188d58…ea8e
2 touches
0 conflicts
0x33018431…8f5d
0x188d58…ea8e
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:
0x754704bc…afb603
1 conflict on slot
0xad092ae66f…95b421
Audit this contract →
← previous block
·
next block →
recent activity