pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,686,869
← previous block
next block →
recent activity
Analyzing
Block #89,686,869
11 transactions · 10 stateful · 2026-07-23 17:08:04 UTC
Parallelism
82
/100
Blocked
10
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,686,869
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x000001e4
· blocks 1
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
#5
0x29eed2d3
#7
execFwdPositionOps
#8
execFwdPositionOps
#9
setData
#10
0xc7e3ec2c
#6
0xce1e7030
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0001
0x4b6ce4…7f37
4 touches
1 conflict
0x00000000…0003
0x4b6ce4…7f37
4 touches
1 conflict
0x6f845aff…9fc9
0x3bd359…433a
4 touches
1 conflict
0x062b2598…4e28
0x43cf54…7777
4 touches
1 conflict
0x00000000…0000
0x4b6ce4…7f37
4 touches
1 conflict
0x44ed742f…63f5
0x3bd359…433a
2 touches
0 conflicts
0x4eb758b8…b13b
0x3bd359…433a
2 touches
0 conflicts
0xc6101b5d…4361
0x3bd359…433a
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:
0x4b6ce40b…657f37
1 conflict on slot
0x0000000000…000001
Audit this contract →
← previous block
·
next block →
recent activity