pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,541,798
← previous block
next block →
recent activity
Analyzing
Block #95,541,798
11 transactions · 9 stateful · 2026-08-13 04:58:35 UTC
Parallelism
82
/100
Blocked
22
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,541,798
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x5acec890
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOps
· blocks 2
#6
repayWithCollateral
#8
setData
#10
0x61d59c2d
#7
execFwdPositionOps
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x7938c6fd…1cd1
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x0dca9548…7024
0x34b655…2a6f
2 touches
0 conflicts
0x2697123c…8526
0x34b655…2a6f
2 touches
0 conflicts
0x34d95d94…3a16
0x34b655…2a6f
2 touches
0 conflicts
0x3610cfd5…236a
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
0xf3d10975b0…050d07
Audit this contract →
← previous block
·
next block →
recent activity