pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#93,355,635
← previous block
next block →
recent activity
Analyzing
Block #93,355,635
10 transactions · 8 stateful · 2026-08-05 13:11:47 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#93,355,635
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
executeBatch
#4
0x3f5c179b
#5
execFwdPositionOps
· blocks 1
#6
repayWithCollateral
#8
modifyLiquidities
#9
0x59558d29
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4406ea71…7fdc
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x634549fe…c16b
0x34b655…2a6f
4 touches
1 conflict
0x69473e5b…cb2a
0x34b655…2a6f
4 touches
1 conflict
0xb5924647…4cf1
0x34b655…2a6f
4 touches
1 conflict
0xd895ee0b…d301
0x34b655…2a6f
4 touches
1 conflict
0xf18fa6c1…4bf8
0x34b655…2a6f
4 touches
1 conflict
0x2385516f…eca5
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
0x4406ea715c…4e7fdc
Audit this contract →
← previous block
·
next block →
recent activity