pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,692,396
← previous block
next block →
recent activity
Analyzing
Block #90,692,396
5 transactions · 5 stateful · 2026-07-27 05:49:27 UTC
Parallelism
60
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,692,396
· 5 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOps
· blocks 1
#4
setData
#3
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x73380965…d0e1
0x34b655…2a6f
4 touches
1 conflict
0xb5f244d5…f550
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0ee13be7…7b2c
0x34b655…2a6f
2 touches
0 conflicts
0x16216d99…518a
0x34b655…2a6f
2 touches
0 conflicts
0x2f0fe1df…da89
0x34b655…2a6f
2 touches
0 conflicts
0x2f0fe1df…da8a
0x34b655…2a6f
2 touches
0 conflicts
0x33649c4f…b327
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
0x733809656f…58d0e1
Audit this contract →
← previous block
·
next block →
recent activity