pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,677,609
← previous block
next block →
recent activity
Analyzing
Block #93,677,609
9 transactions · 8 stateful · 2026-08-06 16:10:26 UTC
Parallelism
67
/100
Blocked
50
%
Avg conflicts / tx
0.44
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,677,609
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x5acec890
· blocks 2
#4
execFwdPositionOps
· blocks 1
#6
updateDataFeedsValuesPartial
#7
setData
#2
0x5acec890
· blocks 1
#3
execOrders
#5
execFwdPositionOps
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w1
4
w0
5
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf4ef5ed7…6451
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd676e291…3ecf
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9416
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x0fb9e50c…1a35
0x34b655…2a6f
4 touches
1 conflict
0x167ed203…48aa
0x34b655…2a6f
4 touches
1 conflict
0x167ed203…48ab
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
1 conflict on slot
0xf4ef5ed7f4…056451
Audit this contract →
← previous block
·
next block →
recent activity