pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,604,388
← previous block
next block →
recent activity
Analyzing
Block #90,604,388
8 transactions · 7 stateful · 2026-07-26 22:26:42 UTC
Parallelism
63
/100
Blocked
29
%
Avg conflicts / tx
0.38
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,604,388
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updatePrices
#2
0x5a5d9a99
· blocks 2
#3
updateDataFeedsValuesPartial
#6
setData
#7
setData
#4
execFwdPositionOps
· blocks 1
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbb322930…ace5
0x34b655…2a6f
4 touches
1 conflict
0xfc3d5171…8357
0x34b655…2a6f
4 touches
1 conflict
0x74ceec2b…6b43
0x34b655…2a6f
4 touches
1 conflict
0x0b5dedb4…e3e8
0x34b655…2a6f
2 touches
0 conflicts
0x0ee63a5d…d67b
0x34b655…2a6f
2 touches
0 conflicts
0x12ca89a3…8993
0x34b655…2a6f
2 touches
0 conflicts
0x16d629d1…d299
0x34b655…2a6f
2 touches
0 conflicts
0x18e86f02…fa98
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
0xbb32293008…46ace5
Audit this contract →
← previous block
·
next block →
recent activity