pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,581,627
← previous block
next block →
recent activity
Analyzing
Block #95,581,627
11 transactions · 9 stateful · 2026-08-13 08:18:53 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,581,627
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
repayWithCollateral
#3
execFwdPositionOps
· blocks 1
#4
0xc925b3a5
#6
0x260595cf
#7
0x6a7d7e65
#8
transfer
#9
setData
#10
execOrders
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66d5e476…8a1f
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0000
0x2970fd…1fc2
2 touches
0 conflicts
0x01d422df…4360
0x34b655…2a6f
2 touches
0 conflicts
0x0728ec77…146c
0x34b655…2a6f
2 touches
0 conflicts
0x3df0422c…fd38
0x34b655…2a6f
2 touches
0 conflicts
0x3df0422c…fd39
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
0x66d5e476c0…268a1f
Audit this contract →
← previous block
·
next block →
recent activity