pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,293,000
← previous block
next block →
recent activity
Analyzing
Block #90,293,000
10 transactions · 10 stateful · 2026-07-25 20:06:41 UTC
Parallelism
70
/100
Blocked
20
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,293,000
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOps
· blocks 2
#5
handleOps
#6
execOrders
#7
transfer
#8
setData
#9
0xc7e3ec2c
#3
execFwdPositionOps
· blocks 1
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xf0ba2726…2371
0x34b655…2a6f
4 touches
1 conflict
0x0aa5e418…5d1d
0x34b655…2a6f
4 touches
1 conflict
0x1416e2fb…e2b3
0x34b655…2a6f
4 touches
1 conflict
0x156ea0a2…0b55
0x34b655…2a6f
4 touches
1 conflict
0x376c9634…97d2
0x34b655…2a6f
4 touches
1 conflict
0x57dcf6f4…1b9c
0x34b655…2a6f
4 touches
1 conflict
0x5ea9eca9…22a6
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
0xbcbf5d09a8…c68bac
Audit this contract →
← previous block
·
next block →
recent activity