pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,323,277
← previous block
next block →
recent activity
Analyzing
Block #90,323,277
9 transactions · 9 stateful · 2026-07-25 22:40:40 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,323,277
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
#4
execFwdPositionOps
· blocks 1
#6
execOrders
#7
updateTemporalNumericValuesV1
#8
setData
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbdc3ef6a…e35e
0x34b655…2a6f
4 touches
1 conflict
0xe30c1f62…49ae
0x34b655…2a6f
4 touches
1 conflict
0x5376f5ee…5daa
0x34b655…2a6f
4 touches
1 conflict
0x53fcfcd4…5c81
0x34b655…2a6f
4 touches
1 conflict
0x53fcfcd4…5c82
0x34b655…2a6f
4 touches
1 conflict
0xc76a2a8f…14cd
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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
1 conflict on slot
0xbdc3ef6a21…66e35e
Audit this contract →
← previous block
·
next block →
recent activity