pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,559,467
← previous block
next block →
recent activity
Analyzing
Block #90,559,467
8 transactions · 8 stateful · 2026-07-26 18:40:43 UTC
Parallelism
63
/100
Blocked
38
%
Avg conflicts / tx
0.5
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,559,467
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOps
· blocks 2
#5
0x6a665523
#6
setData
#3
execFwdPositionOps
· blocks 2
#4
execFwdPositionOps
#7
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4253010a…4700
0x34b655…2a6f
6 touches
3 conflicts
0x66bdb4c2…7ea6
0x34b655…2a6f
6 touches
3 conflicts
0xfa969f55…8bd7
0x34b655…2a6f
4 touches
1 conflict
0x2ee5c07b…7eb9
0x34b655…2a6f
4 touches
1 conflict
0x403fb46d…0d5a
0x34b655…2a6f
4 touches
1 conflict
0x403fb46d…0d5b
0x34b655…2a6f
4 touches
1 conflict
0xba1ef4c2…ef4e
0x34b655…2a6f
4 touches
1 conflict
0xf06cb710…1a9a
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
3 conflicts on slot
0x4253010a01…7a4700
Audit this contract →
← previous block
·
next block →
recent activity