pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#70,877,640
← previous block
next block →
recent activity
Analyzing
Block #70,877,640
11 transactions · 10 stateful · 2026-04-27 13:58:03 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,877,640
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
revealWithCallback
#2
0x98717539
#3
updateDataFeedsValuesPartial
#4
0x6463ffd1
· blocks 1
#6
0x0c7abd22
#7
setData
#8
0x39435dac
#9
updatePrices
#10
updatePrices
#5
0x6463ffd1
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0xffd7f22d…fdd9
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xaccbacf1…d0f3
0x065c9d…c394
4 touches
1 conflict
0x63bd0e6a…72b1
0x065c9d…c394
4 touches
1 conflict
0xa0dbd92f…adbd
0x065c9d…c394
4 touches
1 conflict
0xb037a293…55a0
0x065c9d…c394
3 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
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