pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,872,905
← previous block
next block →
recent activity
Analyzing
Block #89,872,905
10 transactions · 8 stateful · 2026-07-24 08:46:34 UTC
Parallelism
80
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,872,905
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x6ad2e98b
· blocks 1
#4
0x1fe271b4
· blocks 1
#6
execFwdPositionOps
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
setData
#3
0xab083028
#5
0x1fe271b4
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xabc88785…c97b
0x0a2fbf…29b1
4 touches
1 conflict
0xb314615f…4c13
0x0a2fbf…29b1
4 touches
1 conflict
0xb314615f…4c14
0x0a2fbf…29b1
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0005
0x370e2e…63b4
4 touches
1 conflict
0xabc88785…c97a
0x0a2fbf…29b1
4 touches
1 conflict
0xabc88785…c97e
0x0a2fbf…29b1
4 touches
1 conflict
0x1bff683e…7ecb
0x754704…b603
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:
0x0a2fbf2d…f729b1
1 conflict on slot
0xabc88785e9…76c97b
Audit this contract →
← previous block
·
next block →
recent activity