pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,677,987
← previous block
next block →
recent activity
Analyzing
Block #90,677,987
11 transactions · 7 stateful · 2026-07-27 04:36:57 UTC
Parallelism
82
/100
Blocked
14
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,677,987
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execPerpOps
#2
0x5a5d9a99
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
#5
execFwdPositionOps
· blocks 1
#7
0x6a66e0e1
#8
0x6a66e0e1
#9
setData
#10
0xc7e3ec2c
#6
execFwdPositionOps
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
0x0edac7bb…1625
0x34b655…2a6f
4 touches
1 conflict
0x3b56f79b…310f
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x054afe69…16e8
0x34b655…2a6f
2 touches
0 conflicts
0x24b6091e…d294
0x34b655…2a6f
2 touches
0 conflicts
0x32c200d2…c933
0x34b655…2a6f
2 touches
0 conflicts
0x3d4c0233…20a5
0x34b655…2a6f
2 touches
0 conflicts
0x4a6982a4…158c
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:
Perpl
1 conflict on slot
0x0edac7bb51…c71625
Audit this contract →
← previous block
·
next block →
recent activity