pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,204,063
← previous block
next block →
recent activity
Analyzing
Block #90,204,063
9 transactions · 8 stateful · 2026-07-25 12:37:38 UTC
Parallelism
78
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,204,063
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOps
· blocks 2
#5
0x6a64ae8a
#6
setData
#7
execOrders
#8
0xc7e3ec2c
#3
execFwdPositionOps
#4
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x0e987a39…7fe0
0x34b655…2a6f
2 touches
0 conflicts
0x10a3ac20…cd8a
0x34b655…2a6f
2 touches
0 conflicts
0x1a2e31d1…a589
0x34b655…2a6f
2 touches
0 conflicts
0x1c0a8113…1c70
0x34b655…2a6f
2 touches
0 conflicts
0x1eb0fab5…3517
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
0x34a1ee7e95…7cfb20
Audit this contract →
← previous block
·
next block →
recent activity