pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#70,917,593
← previous block
next block →
recent activity
Analyzing
Block #70,917,593
9 transactions · 8 stateful · 2026-04-27 18:24:07 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,917,593
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xb3dd4ec4
#2
updatePrices
#3
0x98717539
#4
updateDataFeedsValuesPartial
#5
0x69efaa3e
#6
setData
#7
0x39435dac
· blocks 1
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x25de453d…9573
0x34b655…2a6f
4 touches
1 conflict
0x9e0e23b5…6910
0x34b655…2a6f
4 touches
1 conflict
0xaf498679…7732
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x01737532…9b12
0x34b655…2a6f
4 touches
1 conflict
0x8956cb26…42fa
0x73ada1…8be0
2 touches
0 conflicts
0x8956cb26…42fd
0x73ada1…8be0
2 touches
0 conflicts
0xa9274bfd…c13d
0x73ada1…8be0
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
0x25de453d2d…559573
Audit this contract →
← previous block
·
next block →
recent activity