pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,864,451
← previous block
next block →
recent activity
Analyzing
Block #90,864,451
10 transactions · 8 stateful · 2026-07-27 20:15:08 UTC
Parallelism
80
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,864,451
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
execFwdPositionOps
· blocks 1
#3
updateDataFeedsValuesPartial
#5
execFwdPositionOps
· blocks 1
#7
0x6a67bcc4
#8
setData
#9
execOrders
#4
execFwdPositionOps
#6
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w1
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x80656e3b…9240
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x033cf007…136d
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
2 touches
0 conflicts
0x2121b1b0…cc4e
0x34b655…2a6f
2 touches
0 conflicts
0x24e3bf88…17bf
0x34b655…2a6f
2 touches
0 conflicts
0x379dc435…6616
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
0x80656e3b9f…e39240
Audit this contract →
← previous block
·
next block →
recent activity