pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,441,232
← previous block
next block →
recent activity
Analyzing
Block #90,441,232
9 transactions · 7 stateful · 2026-07-26 08:45:39 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,441,232
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 1
#4
execFwdPositionOps
#6
updateTemporalNumericValuesV1
#7
setData
#8
exactInputSingle
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc4930bd3…6af2
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xce01223a…3d2e
0x34b655…2a6f
4 touches
1 conflict
0x44df3c2a…baff
0x34b655…2a6f
4 touches
1 conflict
0x44df3c2a…bafe
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0xb9ccd689…c424
0x34b655…2a6f
4 touches
1 conflict
0x3e5604c0…8bc3
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
0xc4930bd393…e46af2
Audit this contract →
← previous block
·
next block →
recent activity