pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,999,582
← previous block
next block →
recent activity
Analyzing
Block #70,999,582
12 transactions · 12 stateful · 2026-04-28 03:30:04 UTC
Parallelism
83
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,999,582
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x69f02a34
#2
multicall
#3
0x98717539
#4
updateDataFeedsValuesPartial
#5
0x6463ffd1
· blocks 1
#6
setData
#7
updatePosition
#9
relay
#10
0x9e76c652
#11
commit
#8
0x6463ffd1
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x18efd065…035c
0x065c9d…c394
4 touches
1 conflict
0xb278abcc…c982
0x065c9d…c394
4 touches
1 conflict
0x92d610a6…9a40
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x1cd169e8…0bb2
0x065c9d…c394
3 touches
1 conflict
0x58fbf623…0e80
0x065c9d…c394
3 touches
1 conflict
0x09000000…0001
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