pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,395,393
← previous block
next block →
recent activity
Analyzing
Block #95,395,393
9 transactions · 6 stateful · 2026-08-12 16:41:21 UTC
Parallelism
78
/100
Blocked
33
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,395,393
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 2
#3
0x57368ddf
#4
updateDataFeedsValuesPartial
#5
0x6a7ca2a9
#6
transfer
#7
setData
#2
execFwdPositionOps
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4efae872…6aa8
0x34b655…2a6f
4 touches
1 conflict
0x4102cb2a…3b17
0x34b655…2a6f
4 touches
1 conflict
0x83f3d320…fb59
0x34b655…2a6f
4 touches
1 conflict
0x953517cb…cdec
0x34b655…2a6f
4 touches
1 conflict
0xcd51eb25…31f9
0x34b655…2a6f
4 touches
1 conflict
0xe4f5cdcb…d942
0x34b655…2a6f
4 touches
1 conflict
0x42b10c57…3ee7
0x34b655…2a6f
2 touches
0 conflicts
0x46483cb1…e7ca
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
0x4efae87285…886aa8
Audit this contract →
← previous block
·
next block →
recent activity