pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#70,995,428
← previous block
next block →
recent activity
Analyzing
Block #70,995,428
8 transactions · 8 stateful · 2026-04-28 03:02:29 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,995,428
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
dagSwapByOrderId
#2
updateDataFeedsValuesPartial
#3
0x6463ffd1
· blocks 1
#5
execute
#6
0x69f023bc
#7
setData
#4
0x6463ffd1
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
0x15376a64…f87d
0x065c9d…c394
4 touches
1 conflict
0x28b2b229…15cd
0x065c9d…c394
4 touches
1 conflict
0xbf009927…c633
0x065c9d…c394
4 touches
1 conflict
0xf4bdcf41…b8b4
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x5b571ba0…f13a
0x368ee5…7ca4
2 touches
0 conflicts
0x1666e4eb…021e
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
0x15376a644e…e9f87d
Audit this contract →
← previous block
·
next block →
recent activity