pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#70,908,154
← previous block
next block →
recent activity
Analyzing
Block #70,908,154
10 transactions · 9 stateful · 2026-04-27 17:21:13 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,908,154
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0x6463ffd1
· blocks 1
#3
setData
#5
0x69ef9b81
#6
0x39435dac
#7
0x39435dac
#8
0x39435dac
#9
0x39435dac
#4
0x6463ffd1
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa0281eb2…a303
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x272533f9…c14e
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x61a1d9ce…2b59
0x065c9d…c394
4 touches
1 conflict
0x9ae25b1f…c976
0x065c9d…c394
4 touches
1 conflict
0x3c9e851c…ed03
0x065c9d…c394
2 touches
1 conflict
0xe5315a5b…b6aa
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0xa0281eb2d0…41a303
Audit this contract →
← previous block
·
next block →
recent activity