pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#70,956,340
← previous block
next block →
recent activity
Analyzing
Block #70,956,340
8 transactions · 8 stateful · 2026-04-27 22:42:00 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,956,340
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x98717539
· blocks 1
#4
updateDataFeedsValuesPartial
#5
0x6463ffd1
#6
0x69efe6af
#7
setData
#3
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x462c8be7…4f83
0x8d66a4…3095
4 touches
1 conflict
0x5ba51e87…44ee
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1ae
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1af
0x8d66a4…3095
4 touches
1 conflict
0x8a35acfb…d1b0
0x8d66a4…3095
4 touches
1 conflict
0x96504a63…52d2
0x8d66a4…3095
4 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
0x09000000…0007
0x000000…1000
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:
0x8d66a43f…113095
1 conflict on slot
0x462c8be7ee…684f83
Audit this contract →
← previous block
·
next block →
recent activity