pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#106,191,848
← previous block
next block →
recent activity
Analyzing
Block #106,191,848
11 transactions · 11 stateful · 2026-09-19 13:42:33 UTC
Parallelism
82
/100
Blocked
18
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#106,191,848
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updatePrices
#2
execOrders
#3
0x5acec890
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOpsV2
· blocks 1
#6
execFwdPositionOpsV2
#8
transferWithAuthorization
· blocks 1
#10
setData
#7
execFwdPositionOpsV2
#9
transferWithAuthorization
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x1eb0fab5…3517
0x34b655…2a6f
2 touches
0 conflicts
0x29c7f30c…f1dd
0x34b655…2a6f
2 touches
0 conflicts
0x2dfc834d…12be
0x34b655…2a6f
2 touches
0 conflicts
0x308e9feb…a07c
0x34b655…2a6f
2 touches
0 conflicts
0x31f91762…6419
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
0x482471adbb…39122f
Audit this contract →
← previous block
·
next block →
recent activity