pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,528,897
← previous block
next block →
recent activity
Analyzing
Block #95,528,897
11 transactions · 10 stateful · 2026-08-13 03:53:41 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,528,897
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
execute
#3
execute
#4
0xab083028
· blocks 1
#6
execOrders
#7
updateDataFeedsValuesPartial
#8
0x222d4ad6
#9
execFwdPositionOps
· blocks 1
#5
0x8263f5d9
#10
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbb97db90…4c93
0xc8689a…ee79
4 touches
1 conflict
0x98d1e7bb…8483
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xdc8d7edd…8a03
0x34b655…2a6f
4 touches
1 conflict
0x16c788ed…28e5
0x065c9d…c394
2 touches
0 conflicts
0x3b22fe2c…32fa
0x065c9d…c394
2 touches
0 conflicts
0xb33ff823…1188
0x065c9d…c394
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: Settlement / Helper
1 conflict on slot
0xbb97db90cd…304c93
Audit this contract →
← previous block
·
next block →
recent activity