pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,587,140
← previous block
next block →
recent activity
Analyzing
Block #95,587,140
11 transactions · 10 stateful · 2026-08-13 08:46:37 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,587,140
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 1
#5
executeBatch
· blocks 1
#7
transfer
#8
0x6a7d84e5
#9
setData
#10
0x59558d29
#4
execFwdPositionOps
#6
executeBatch
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0xc4cfda13…e500
0xe52b14…7230
3 touches
1 conflict
0x168f75b5…b2d1
0x34b655…2a6f
2 touches
0 conflicts
0x1b4aa556…0d2b
0x34b655…2a6f
2 touches
0 conflicts
0x448a51f4…1a6d
0x34b655…2a6f
2 touches
0 conflicts
0x74ba5890…79bc
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
0xbcbf5d09a8…c68bac
Audit this contract →
← previous block
·
next block →
recent activity