pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,670,349
← previous block
next block →
recent activity
Analyzing
Block #87,670,349
10 transactions · 9 stateful · 2026-07-14 09:10:42 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,670,349
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
execute
#4
execute
#5
forward
#6
execFwdPositionOps
· blocks 1
#9
setData
#7
execFwdPositionOps
· blocks 1
#8
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6ed9a3c3…001d
0x34b655…2a6f
4 touches
1 conflict
0xa182a3e0…1c68
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x6ed9a3c3…001e
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5de7f4e0…c7cd
0x34b655…2a6f
4 touches
1 conflict
0x5e4a329f…bc40
0x34b655…2a6f
4 touches
1 conflict
0x65cd6e4a…2725
0x34b655…2a6f
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:
Perpl
1 conflict on slot
0x6ed9a3c342…2e001d
Audit this contract →
← previous block
·
next block →
recent activity