pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#70,995,646
← previous block
next block →
recent activity
Analyzing
Block #70,995,646
7 transactions · 7 stateful · 2026-04-28 03:03:56 UTC
Parallelism
71
/100
Blocked
14
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,995,646
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
transferAndMulticall
#2
0x98717539
#3
updateDataFeedsValuesPartial
#4
setData
#5
0x6463ffd1
· blocks 1
#6
0x6463ffd1
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x1c6f8b9b…8068
0x065c9d…c394
4 touches
1 conflict
0x595742c5…b02e
0x065c9d…c394
4 touches
1 conflict
0x8258caa5…440b
0x065c9d…c394
4 touches
1 conflict
0xfe352ec6…c6af
0x065c9d…c394
4 touches
1 conflict
0xde2adf17…c62f
0x000000…012a
2 touches
0 conflicts
0x00000000…0006
0x736237…034f
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:
0xd0f8a642…83badc
1 conflict on slot
0x0000000000…000004
Audit this contract →
← previous block
·
next block →
recent activity