pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,530,215
← previous block
next block →
recent activity
Analyzing
Block #95,530,215
9 transactions · 9 stateful · 2026-08-13 04:00:19 UTC
Parallelism
78
/100
Blocked
22
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,530,215
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 2
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#6
execFwdPositionOps
#7
0x6a7d41ca
#8
setData
#2
0x5acec890
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8cd684d0…c3cb
0x34b655…2a6f
4 touches
1 conflict
0x966e45cf…0f25
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x0f748762…24ce
0x34b655…2a6f
2 touches
0 conflicts
0x1c93cd52…1538
0x34b655…2a6f
2 touches
0 conflicts
0x24521815…c677
0x34b655…2a6f
2 touches
0 conflicts
0x25a6f828…73ce
0x34b655…2a6f
2 touches
0 conflicts
0x36890fff…f3d1
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
0x8cd684d0d7…f5c3cb
Audit this contract →
← previous block
·
next block →
recent activity