pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,383,921
← previous block
next block →
recent activity
Analyzing
Block #90,383,921
10 transactions · 10 stateful · 2026-07-26 03:51:11 UTC
Parallelism
70
/100
Blocked
20
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,383,921
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x6a6584a7
#2
0x5a5d9a99
· blocks 2
#4
updateDataFeedsValuesPartial
#5
0xed82b078
#7
execOrders
#8
setData
#9
0xc7e3ec2c
#3
execFwdPositionOps
· blocks 1
#6
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x94bb14fe…8f47
0x34b655…2a6f
6 touches
3 conflicts
0xec1a6fa7…e1f8
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0aa5e418…5d1d
0x34b655…2a6f
2 touches
0 conflicts
0x5854460c…c9d1
0x34b655…2a6f
2 touches
0 conflicts
0x613b15a5…d6c8
0x34b655…2a6f
2 touches
0 conflicts
0x6713b018…05f3
0x34b655…2a6f
2 touches
0 conflicts
0x6fe7d366…78ff
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
0x94bb14fe40…668f47
Audit this contract →
← previous block
·
next block →
recent activity