pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#70,878,575
← previous block
next block →
recent activity
Analyzing
Block #70,878,575
8 transactions · 8 stateful · 2026-04-27 14:04:17 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,878,575
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
0x98717539
#3
0x6463ffd1
· blocks 1
#5
forward
#6
updateDataFeedsValuesPartial
#7
setData
#4
0x6463ffd1
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xab1a3ce9…dfbb
0x065c9d…c394
4 touches
1 conflict
0xf97a7ac0…ec93
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x6b861125…0a00
0x065c9d…c394
3 touches
1 conflict
0x7420b8f1…e0eb
0x065c9d…c394
3 touches
1 conflict
0x904fc3c0…00ec
0x34b655…2a6f
2 touches
0 conflicts
0x94e7f277…471b
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0xab1a3ce9d6…78dfbb
Audit this contract →
← previous block
·
next block →
recent activity