pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,585,040
← previous block
next block →
recent activity
Analyzing
Block #95,585,040
13 transactions · 10 stateful · 2026-08-13 08:36:03 UTC
Parallelism
85
/100
Blocked
20
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,585,040
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execPerpOps
#2
execPerpOps
#3
0x5acec890
#4
execFwdPositionOps
#5
execFwdPositionOps
#6
executeBatch
· blocks 1
#8
updateDataFeedsValuesPartial
#9
setData
#10
execOrders
#11
execOrders
· blocks 1
#7
executeBatch
#12
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
11
w0
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x427dec7f…61c6
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x14b6f855…d461
0x34b655…2a6f
4 touches
1 conflict
0x2a5e2b11…1c2b
0x34b655…2a6f
4 touches
1 conflict
0x0b0c2e8d…c1b8
0xe52b14…7230
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0x91934f74…4788
0xe52b14…7230
3 touches
1 conflict
0x09000000…0001
0x000000…1000
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
0x427dec7fbc…3e61c6
Audit this contract →
← previous block
·
next block →
recent activity