pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#70,908,336
← previous block
next block →
recent activity
Analyzing
Block #70,908,336
9 transactions · 8 stateful · 2026-04-27 17:22:26 UTC
Parallelism
78
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,908,336
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
addLiquidity
#3
0x98717539
· blocks 1
#4
updateDataFeedsValuesPartial
#5
0x6463ffd1
· blocks 1
#7
setData
#6
0x6463ffd1
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w0
6
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xad85f939…1c39
0x065c9d…c394
4 touches
1 conflict
0xbb1747e2…f78b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x010fda3f…6fca
0x065c9d…c394
4 touches
1 conflict
0x38ba9ea1…9262
0x065c9d…c394
4 touches
1 conflict
0x64edd399…7714
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x4039b31f…0f4a
0x754704…b603
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:
0x065c9d28…a9c394
1 conflict on slot
0xad85f93993…551c39
Audit this contract →
← previous block
·
next block →
recent activity