pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,286,204
← previous block
next block →
recent activity
Analyzing
Block #90,286,204
7 transactions · 6 stateful · 2026-07-25 19:32:11 UTC
Parallelism
71
/100
Blocked
17
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,286,204
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 1
#5
setData
#6
execOrders
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x046e4d12…847a
0x34b655…2a6f
2 touches
0 conflicts
0x060b2fd1…75b6
0x34b655…2a6f
2 touches
0 conflicts
0x0bc506f8…92a2
0x34b655…2a6f
2 touches
0 conflicts
0x0d1e39a9…b40c
0x34b655…2a6f
2 touches
0 conflicts
0x1534b8cf…d0fb
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
0x92385428ad…dc6941
Audit this contract →
← previous block
·
next block →
recent activity