pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#70,999,092
← previous block
next block →
recent activity
Analyzing
Block #70,999,092
8 transactions · 7 stateful · 2026-04-28 03:26:49 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,999,092
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
0x6463ffd1
· blocks 1
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
setData
#7
0x69f02970
#3
0x6463ffd1
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
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x620e09b3…7cd5
0x065c9d…c394
4 touches
1 conflict
0x2a24d18a…56c1
0x065c9d…c394
4 touches
1 conflict
0x35d9a523…b36b
0x065c9d…c394
4 touches
1 conflict
0xd9b44ea5…445d
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x6b3f84e3…e2a9
0x065c9d…c394
2 touches
1 conflict
0xdef7bed4…3981
0x065c9d…c394
2 touches
1 conflict
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