pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,233,921
← previous block
next block →
recent activity
Analyzing
Block #90,233,921
10 transactions · 8 stateful · 2026-07-25 15:08:09 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,233,921
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
0xee83e0a5
#3
0x9e76c652
#4
execFwdPositionOps
#5
execFwdPositionOps
· blocks 1
#6
execFwdPositionOps
#8
setData
#9
execOrders
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x72da4494…8b2f
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe0e2ffb5…9e33
0x34b655…2a6f
4 touches
1 conflict
0x0d5f2460…552c
0x2ab50b…5c41
2 touches
0 conflicts
0x101fda53…7bd7
0x2ab50b…5c41
2 touches
0 conflicts
0x19a19bf7…2788
0x2ab50b…5c41
2 touches
0 conflicts
0x215ae36a…a875
0x2ab50b…5c41
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
0x72da4494e0…358b2f
Audit this contract →
← previous block
·
next block →
recent activity