pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,622,544
← previous block
next block →
recent activity
Analyzing
Block #90,622,544
7 transactions · 7 stateful · 2026-07-26 23:58:02 UTC
Parallelism
57
/100
Blocked
29
%
Avg conflicts / tx
0.29
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,622,544
· 7 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOps
· blocks 1
#4
verifyOracleProofV2
#6
setData
#3
execFwdPositionOps
· blocks 1
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70b7b52e…7743
0x34b655…2a6f
4 touches
1 conflict
0x93b6fab0…09d6
0x34b655…2a6f
4 touches
1 conflict
0x05a510e8…1bb1
0x34b655…2a6f
4 touches
1 conflict
0x98d0d670…2629
0x34b655…2a6f
3 touches
1 conflict
0x2101287f…3f9d
0x34b655…2a6f
2 touches
0 conflicts
0x217bd767…b79e
0x34b655…2a6f
2 touches
0 conflicts
0x2e6c7be1…d3e9
0x34b655…2a6f
2 touches
0 conflicts
0x3347cbe5…846c
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
0x70b7b52e5b…0a7743
Audit this contract →
← previous block
·
next block →
recent activity