pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,298,276
← previous block
next block →
recent activity
Analyzing
Block #95,298,276
9 transactions · 7 stateful · 2026-08-12 08:29:22 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,298,276
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 1
#2
execFwdPositionOps
#4
updateDataFeedsValuesPartial
#5
0x6a7c2f5a
#6
deposit
#7
setData
#8
0x61633731
#3
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x660d9107…f97f
0x34b655…2a6f
4 touches
1 conflict
0x6b89ce6f…cc35
0x34b655…2a6f
4 touches
1 conflict
0x660d9107…f980
0x34b655…2a6f
4 touches
1 conflict
0x8606b8cc…a4e0
0x34b655…2a6f
4 touches
1 conflict
0xfb217e61…2614
0x34b655…2a6f
4 touches
1 conflict
0x28c180e1…f1e2
0x34b655…2a6f
2 touches
0 conflicts
0x30fe4e5c…664b
0x34b655…2a6f
2 touches
0 conflicts
0x3302301d…6eb3
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
0x660d910745…c4f97f
Audit this contract →
← previous block
·
next block →
recent activity