pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#94,663,410
← previous block
next block →
recent activity
Analyzing
Block #94,663,410
11 transactions · 8 stateful · 2026-08-10 03:04:29 UTC
Parallelism
82
/100
Blocked
25
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#94,663,410
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
0x5acec890
· blocks 2
#4
updateDataFeedsValuesPartial
#6
0xed82b078
#7
0x6a794035
#8
setData
#9
0x1cb3d5…4415
#10
execOrders
#3
0x5acec890
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3383813…4a0c
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x0610892c…fee0
0x34b655…2a6f
2 touches
0 conflicts
0x0cc1a3f1…71db
0x34b655…2a6f
2 touches
0 conflicts
0x111007c2…d736
0x34b655…2a6f
2 touches
0 conflicts
0x1679b116…c99d
0x34b655…2a6f
2 touches
0 conflicts
0x38c6ff01…689f
0x34b655…2a6f
2 touches
0 conflicts
0x76a66a12…3513
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
0xf338381336…ec4a0c
Audit this contract →
← previous block
·
next block →
recent activity