pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,456,063
← previous block
next block →
recent activity
Analyzing
Block #90,456,063
9 transactions · 9 stateful · 2026-07-26 10:00:32 UTC
Parallelism
67
/100
Blocked
33
%
Avg conflicts / tx
0.56
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,456,063
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
0x5a5d9a99
· blocks 1
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 2
#6
setData
#5
execFwdPositionOps
· blocks 2
#7
execFwdPositionOps
#8
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w0
5
w1
7
w2
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x17637b08…707f
0x34b655…2a6f
4 touches
1 conflict
0x3ac0ead0…e0e3
0x34b655…2a6f
4 touches
1 conflict
0x5a36d0c8…12e2
0x34b655…2a6f
4 touches
1 conflict
0x5a36d0c8…12e3
0x34b655…2a6f
4 touches
1 conflict
0x5af098c7…4806
0x34b655…2a6f
4 touches
1 conflict
0x5af098c7…4807
0x34b655…2a6f
4 touches
1 conflict
0x6633b183…24d3
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
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity