pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,129,001
← previous block
next block →
recent activity
Analyzing
Block #95,129,001
15 transactions · 10 stateful · 2026-08-11 18:08:41 UTC
Parallelism
87
/100
Blocked
10
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,129,001
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execPerpOps
#2
execPerpOps
#3
updateDataFeedsValuesPartial
#4
execOrders
#5
execOrders
#6
0x6a7b65a1
#7
execFwdPositionOps
#8
executeBatch
#9
execFwdPositionOps
#10
resolve
#11
setData
· blocks 1
#13
execOrders
#14
execOrders
#12
setData
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
11
w0
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1889bdd1…e092
0x34b655…2a6f
2 touches
0 conflicts
0x4922f298…f280
0x34b655…2a6f
2 touches
0 conflicts
0x4b76146e…0dcb
0x34b655…2a6f
2 touches
0 conflicts
0x4b8db3ce…d59b
0x34b655…2a6f
2 touches
0 conflicts
0x7e5ea60a…c4a1
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:
0x33176be2…ede078
1 conflict on slot
0x09106a952c…111467
Audit this contract →
← previous block
·
next block →
recent activity