pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#70,911,592
← previous block
next block →
recent activity
Analyzing
Block #70,911,592
13 transactions · 10 stateful · 2026-04-27 17:44:07 UTC
Parallelism
85
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,911,592
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
trade
#2
0x0f052239
· blocks 1
#3
depositNative
#4
0x98717539
#5
poke
#6
updateDataFeedsValuesPartial
#7
0xe7be4706
#8
0xe7be4706
#10
setData
#11
0x39435dac
#12
updatePrices
#9
0x0c7abd22
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8876d94c…8435
0x2a68ba…90c5
4 touches
1 conflict
0x6f849c4f…1646
0xa6afd3…d132
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x2e4ae358…3a64
0x065c9d…c394
2 touches
0 conflicts
0xc3c8642a…7da5
0x2a68ba…90c5
2 touches
0 conflicts
0x74fe76c9…225f
0x3bd359…433a
2 touches
0 conflicts
0xa980598e…ec52
0x3bd359…433a
2 touches
0 conflicts
0x5d8373b9…233d
0x44b60b…f711
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:
0x2a68ba18…8e90c5
1 conflict on slot
0x8876d94c2a…cc8435
Audit this contract →
← previous block
·
next block →
recent activity