pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,188,107
← previous block
next block →
recent activity
Analyzing
Block #93,188,107
10 transactions · 10 stateful · 2026-08-04 23:09:30 UTC
Parallelism
70
/100
Blocked
20
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,188,107
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
batchUpdate
#2
execFwdPositionOps
· blocks 2
#5
updateDataFeedsValuesPartial
#6
0x6a7271a2
#7
setData
#8
execOrders
#9
0x59558d29
#3
execFwdPositionOps
· blocks 1
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfecb18c0…01ed
0x34b655…2a6f
6 touches
3 conflicts
0xf28ee159…1f3b
0x34b655…2a6f
4 touches
1 conflict
0xf9f7db90…d034
0x34b655…2a6f
4 touches
1 conflict
0x2ffa752b…475e
0x34b655…2a6f
4 touches
1 conflict
0x388b63a9…5008
0x34b655…2a6f
4 touches
1 conflict
0x60a536a6…ef7a
0x34b655…2a6f
4 touches
1 conflict
0x709c2293…6c55
0x34b655…2a6f
4 touches
1 conflict
0x709c2293…6c56
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot
0xfecb18c068…6e01ed
Audit this contract →
← previous block
·
next block →
recent activity