pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#70,877,794
← previous block
next block →
recent activity
Analyzing
Block #70,877,794
10 transactions · 9 stateful · 2026-04-27 13:59:05 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,877,794
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x1a945f9c
· blocks 1
#3
0x6463ffd1
#4
0x0c7abd22
#5
closeTrade
#6
updateDataFeedsValuesPartial
#7
transfer
#8
setData
#9
updatePrices
#2
0x77813803
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x455b104f…3960
0xea1b8e…c5ec
4 touches
1 conflict
0xa8abcc19…3d83
0xea1b8e…c5ec
4 touches
1 conflict
0xbc33a929…8b24
0xea1b8e…c5ec
4 touches
1 conflict
0xd8eb2d31…2ac0
0xea1b8e…c5ec
4 touches
1 conflict
0xeef70cb9…5de7
0xea1b8e…c5ec
4 touches
1 conflict
0x00bac013…a28c
0xfd44b3…00d1
4 touches
1 conflict
0x90cb67d6…bf25
0x1efe02…37d6
2 touches
0 conflicts
0x00000000…0099
0xaa3145…feec
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:
0xea1b8e4a…8fc5ec
1 conflict on slot
0x455b104f81…2e3960
Audit this contract →
← previous block
·
next block →
recent activity