pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,705,349
← previous block
next block →
recent activity
Analyzing
Block #90,705,349
10 transactions · 8 stateful · 2026-07-27 06:54:36 UTC
Parallelism
70
/100
Blocked
25
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,705,349
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
execFwdPositionOps
· blocks 2
#3
execFwdPositionOps
#4
0x3f5c179b
#6
forward
#8
updateDataFeedsValuesPartial
#9
setData
#5
execFwdPositionOps
· blocks 1
#7
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4fb92dc1…2ef7
0x34b655…2a6f
6 touches
3 conflicts
0x32bfa423…362a
0x34b655…2a6f
4 touches
1 conflict
0xb7aced05…46bd
0x34b655…2a6f
4 touches
1 conflict
0x7b0665e8…fbdf
0x34b655…2a6f
4 touches
1 conflict
0x0494220d…abf7
0x34b655…2a6f
2 touches
0 conflicts
0x23b19153…fe5d
0x34b655…2a6f
2 touches
0 conflicts
0x52369588…a969
0x34b655…2a6f
2 touches
0 conflicts
0x53d6f1c9…16c4
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
3 conflicts on slot
0x4fb92dc1c2…a62ef7
Audit this contract →
← previous block
·
next block →
recent activity