pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,510,708
← previous block
next block →
recent activity
Analyzing
Block #93,510,708
10 transactions · 10 stateful · 2026-08-06 02:11:25 UTC
Parallelism
70
/100
Blocked
30
%
Avg conflicts / tx
0.4
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,510,708
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrders
#2
execFwdPositionOps
· blocks 2
#4
0x3f5c179b
· blocks 1
#6
0xed82b078
#8
updateDataFeedsValuesPartial
#9
setData
#3
execFwdPositionOps
· blocks 1
#5
batchUpdate
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w0
5
w1
7
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xac8a5059…fd42
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x1e302fd3…642c
0x34b655…2a6f
2 touches
0 conflicts
0x27cc7ce7…890d
0x34b655…2a6f
2 touches
0 conflicts
0x2ad29b13…92e0
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
3 conflicts on slot
0xc824469a90…af6425
Audit this contract →
← previous block
·
next block →
recent activity