pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,717,735
← previous block
next block →
recent activity
Analyzing
Block #94,717,735
12 transactions · 10 stateful · 2026-08-10 07:37:43 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,717,735
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 1
#2
updateDataFeedsValuesPartial
#3
updatePriceFeedsIfNecessary
#4
0xd62522e3
#5
execFwdPositionOps
#7
0x6a79803f
#8
transfer
#9
setData
#10
execOrders
#11
execOrders
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3af942da…b842
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1cf56961…b106
0x34b655…2a6f
2 touches
0 conflicts
0x26099e72…f13d
0x34b655…2a6f
2 touches
0 conflicts
0x2b75d304…d186
0x34b655…2a6f
2 touches
0 conflicts
0x379dc435…6616
0x34b655…2a6f
2 touches
0 conflicts
0x48203298…65cb
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
0x3af942daf2…67b842
Audit this contract →
← previous block
·
next block →
recent activity