pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#70,999,389
← previous block
next block →
recent activity
Analyzing
Block #70,999,389
12 transactions · 9 stateful · 2026-04-28 03:28:47 UTC
Parallelism
83
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,999,389
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5bf9264c
#2
0x5bf9264c
#3
exactInputSingle
#4
updateDataFeedsValuesPartial
#5
0x6463ffd1
· blocks 1
#6
0x0c7abd22
#8
forward
#9
commit
#10
0x69f029e6
#11
setData
#7
0x6463ffd1
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x11b4e8e8…9d4a
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x28e59e33…0ce6
0x065c9d…c394
4 touches
1 conflict
0x8d44d1e7…4f0e
0x065c9d…c394
4 touches
1 conflict
0xaa02277c…538e
0x065c9d…c394
4 touches
1 conflict
0x78012fdb…f210
0x065c9d…c394
2 touches
1 conflict
0x01c0e56a…484f
0x065c9d…c394
2 touches
1 conflict
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
0x11b4e8e8c8…f49d4a
Audit this contract →
← previous block
·
next block →
recent activity