pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,892,114
← previous block
next block →
recent activity
Analyzing
Block #70,892,114
10 transactions · 8 stateful · 2026-04-27 15:34:22 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,892,114
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
multicall
#2
updateDataFeedsValuesPartial
#3
0x0c7abd22
· blocks 1
#5
handleOps
#6
approve
#7
setData
#8
signIn
#9
updatePrices
#4
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x6ea8fa8d…3dd8
0x1b6862…e19c
4 touches
1 conflict
0x95c16f5c…8121
0xd32edf…ff58
3 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
0x2af5f63a…b7b9
0x2e3234…7d90
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:
0x1b68626d…2de19c
1 conflict on slot
0x0000000000…000013
Audit this contract →
← previous block
·
next block →
recent activity