pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#70,892,599
← previous block
next block →
recent activity
Analyzing
Block #70,892,599
5 transactions · 5 stateful · 2026-04-27 15:37:36 UTC
Parallelism
60
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#70,892,599
· 5 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6463ffd1
· blocks 1
#3
updatePriceFeedsIfNecessary
#4
setData
#2
0x6463ffd1
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x67b938a0…d254
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x89f127c2…72de
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x1b389a49…d6d3
0x065c9d…c394
4 touches
1 conflict
0x1e0ab5c2…a5db
0x065c9d…c394
4 touches
1 conflict
0xb0ec1f76…b281
0x065c9d…c394
2 touches
1 conflict
0x6ecaaece…b6f2
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
0x67b938a0f9…36d254
Audit this contract →
← previous block
·
next block →
recent activity