pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,996,345
← previous block
next block →
recent activity
Analyzing
Block #70,996,345
12 transactions · 11 stateful · 2026-04-28 03:08:35 UTC
Parallelism
83
/100
Blocked
18
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,996,345
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0xb3dd4ec4
· blocks 1
#3
0x98717539
#4
updateDataFeedsValuesPartial
#5
0x6463ffd1
· blocks 1
#6
setData
#8
forward
#9
modifyLiquidities
#11
0x39435dac
#7
0xb0435a94
#10
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w0
7
w1
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3dc6f35…13e9
0x754704…b603
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5c8c6ab6…dc36
0x065c9d…c394
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
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
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
0xa3dc6f3549…9513e9
Audit this contract →
← previous block
·
next block →
recent activity