pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,872,965
← previous block
next block →
recent activity
Analyzing
Block #89,872,965
13 transactions · 12 stateful · 2026-07-24 08:46:53 UTC
Parallelism
85
/100
Blocked
8
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,872,965
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
executeBatch
#5
0xce1e7030
· blocks 1
#7
forward
#8
forward
#9
execFwdPositionOps
#10
execFwdPositionOps
#11
0x0cf032c6
#12
setData
#6
0xce1e7030
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x714a26…182d
4 touches
1 conflict
0x00000000…0001
0x714a26…182d
4 touches
1 conflict
0x00000000…0003
0x714a26…182d
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xddc22bc2…7f7a
0x754704…b603
4 touches
1 conflict
0x392a02b5…0019
0x81a224…7777
4 touches
1 conflict
0xd06cc746…27e4
0x81a224…7777
4 touches
1 conflict
0xec1f25a1…2b0c
0x065c9d…c394
4 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:
0x714a2694…f2182d
1 conflict on slot
0x0000000000…000000
Audit this contract →
← previous block
·
next block →
recent activity