pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,266,058
← previous block
next block →
recent activity
Analyzing
Block #99,266,058
12 transactions · 10 stateful · 2026-08-26 07:12:01 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
#99,266,058
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
execOrders
#3
0x5acec890
#4
execOrders
#5
0x59558d29
#6
execFwdPositionOpsV2
· blocks 1
#8
batchUpdate
#9
0x57368ddf
#10
execFwdPositionOpsV2
#11
setData
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4a270745…5cc9
0x34b655…2a6f
4 touches
1 conflict
0x76622fb2…4f08
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x208c1363…c653
0x34b655…2a6f
2 touches
0 conflicts
0x25f0fcba…ca8b
0x34b655…2a6f
2 touches
0 conflicts
0x2be34971…27ba
0x34b655…2a6f
2 touches
0 conflicts
0x3870d8f3…29a9
0x34b655…2a6f
2 touches
0 conflicts
0x3f152ba8…cea6
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
0x4a270745c3…fc5cc9
Audit this contract →
← previous block
·
next block →
recent activity