pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,937,223
← previous block
next block →
recent activity
Analyzing
Block #101,937,223
12 transactions · 11 stateful · 2026-09-04 15:33:32 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,937,223
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
execOrders
· blocks 1
#4
0xb2d4797b
#5
setData
#6
0xc0c16b76
#7
execFwdPositionOpsV2
#8
execFwdPositionOpsV2
#9
batchUpdatePrice
#10
execOrders
#11
modifyLiquidities
#3
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc52785b9…08f8
0x34b655…2a6f
4 touches
1 conflict
0xd07b013b…90cb
0x34b655…2a6f
4 touches
1 conflict
0xd98afa6e…3364
0x34b655…2a6f
4 touches
1 conflict
0xfcd7574f…a3a2
0x34b655…2a6f
4 touches
1 conflict
0x1513b999…b52e
0x34b655…2a6f
4 touches
1 conflict
0x2f737feb…aab0
0x34b655…2a6f
4 touches
1 conflict
0x7fd951f1…fe49
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
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
0xc52785b9ae…bc08f8
Audit this contract →
← previous block
·
next block →
recent activity