pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#70,863,636
← previous block
next block →
recent activity
Analyzing
Block #70,863,636
8 transactions · 8 stateful · 2026-04-27 12:24:46 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,863,636
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x98717539
#2
0x6463ffd1
· blocks 1
#4
0x96e62922
#5
forward
#6
updateDataFeedsValuesPartial
#7
setData
#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
0xa8286f40…1016
0x065c9d…c394
4 touches
1 conflict
0xbd47d7d4…3417
0x065c9d…c394
4 touches
1 conflict
0xcc8305ba…86bc
0x065c9d…c394
4 touches
1 conflict
0xd5b8f9b3…9e84
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x414e9446…4b59
0x34b655…2a6f
2 touches
0 conflicts
0x904fc3c0…00ec
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
0xa8286f40dc…231016
Audit this contract →
← previous block
·
next block →
recent activity