pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,846,096
← previous block
next block →
recent activity
Analyzing
Block #70,846,096
8 transactions · 7 stateful · 2026-04-27 10:27:54 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,846,096
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5bf9264c
#2
0x5bf9264c
#3
0x98717539
#4
0x6463ffd1
· blocks 1
#5
updateDataFeedsValuesPartial
#6
setData
#7
0x6463ffd1
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x2da62d94…1a13
0x065c9d…c394
4 touches
1 conflict
0x49ea1d5a…45c2
0x065c9d…c394
4 touches
1 conflict
0x4e92e171…5d79
0x065c9d…c394
4 touches
1 conflict
0x76d7c819…c771
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