pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,951,598
← previous block
next block →
recent activity
Analyzing
Block #70,951,598
9 transactions · 9 stateful · 2026-04-27 22:10:26 UTC
Parallelism
78
/100
Blocked
22
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,951,598
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
revealWithCallback
#2
0x69efdf49
#3
0x39435dac
· blocks 1
#4
updateDataFeedsValuesPartial
#5
0xed82b078
· blocks 1
#7
setData
#6
0xed82b078
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w0
6
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x5c8c6ab6…dc36
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…013a
0xd45826…f134
2 touches
0 conflicts
0x8ebf69ec…edd3
0xd45826…f134
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:
0x34b6552d…112a6f
1 conflict on slot
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity