pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,862,497
← previous block
next block →
recent activity
Analyzing
Block #70,862,497
9 transactions · 9 stateful · 2026-04-27 12:17:11 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,862,497
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x98717539
#3
mintCube
#4
0x6463ffd1
· blocks 1
#5
updateDataFeedsValuesPartial
#7
setData
#8
0x39435dac
#6
0x6463ffd1
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x3f601ca0…1e8f
0x065c9d…c394
4 touches
1 conflict
0x52654d48…17fa
0x065c9d…c394
4 touches
1 conflict
0xb587cf5f…719a
0x065c9d…c394
4 touches
1 conflict
0xd8786952…a0d0
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
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
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity