pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,236,388
← previous block
next block →
recent activity
Analyzing
Block #90,236,388
10 transactions · 10 stateful · 2026-07-25 15:20:35 UTC
Parallelism
80
/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,236,388
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 1
#2
execFwdPositionOps
#3
executeBatch
· blocks 1
#6
0xed82b078
#7
updateDataFeedsValuesPartial
#8
setData
#9
execOrders
#4
executeBatch
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w0
4
w1
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0xb016034c…4b9d
0xe52b14…7230
3 touches
1 conflict
0x0c25b3bc…5775
0x34b655…2a6f
2 touches
0 conflicts
0x31b39922…1e65
0x34b655…2a6f
2 touches
0 conflicts
0x3550075a…fb0f
0x34b655…2a6f
2 touches
0 conflicts
0x36a76bd2…1fb0
0x34b655…2a6f
2 touches
0 conflicts
0x436d7385…abd0
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
0x31b3992285…921e66
Audit this contract →
← previous block
·
next block →
recent activity