pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,991,201
← previous block
next block →
recent activity
Analyzing
Block #101,991,201
12 transactions · 12 stateful · 2026-09-04 20:07:22 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,991,201
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrders
#2
execOrders
· blocks 2
#3
updatePrices
#4
0xab083028
#5
0x59558d29
#7
setData
#8
execFwdPositionOpsV2
#9
0xc925b3a5
#10
0x6a9b2572
#6
execFwdPositionOpsV2
· blocks 1
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
6
w1
11
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x65903ef9…2567
0x34b655…2a6f
6 touches
3 conflicts
0xac206e47…ef7d
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x65f011a5…bc6e
0x34b655…2a6f
2 touches
0 conflicts
0x7daf6443…fd36
0x34b655…2a6f
2 touches
0 conflicts
0x85ca9028…99fc
0x34b655…2a6f
2 touches
0 conflicts
0x8bf661cb…bcd2
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
3 conflicts on slot
0x65903ef9a0…7d2567
Audit this contract →
← previous block
·
next block →
recent activity