pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,892,093
← previous block
next block →
recent activity
Analyzing
Block #70,892,093
10 transactions · 9 stateful · 2026-04-27 15:34:14 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,892,093
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
0x98717539
· blocks 1
#5
updateDataFeedsValuesPartial
#6
execute
#7
0x6463ffd1
#8
setData
#9
0x69ef826e
#3
0x98717539
· blocks 1
#4
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x468c69b1…af11
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1b0
0x8d66a4…3095
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…0002
0xb857c1…9be1
2 touches
0 conflicts
0x0520da1d…c88e
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:
0x34b6552d…112a6f
1 conflict on slot
0x60f7fbaf90…97bd58
Audit this contract →
← previous block
·
next block →
recent activity