pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,536,366
← previous block
next block →
recent activity
Analyzing
Block #95,536,366
12 transactions · 10 stateful · 2026-08-13 04:31:16 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,536,366
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
0x5acec890
· blocks 1
#4
execFwdPositionOps
#5
updateDataFeedsValuesPartial
#6
executeBatch
#7
updateDataFeedsValuesPartial
#8
0x6a7d490c
#9
setData
#10
execute
#11
0x59558d29
#3
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x966e45cf…0f25
0x34b655…2a6f
4 touches
1 conflict
0xe2267a44…fb98
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x0903ab0b…2eac
0x34b655…2a6f
2 touches
0 conflicts
0x0f748762…24ce
0x34b655…2a6f
2 touches
0 conflicts
0x289e1312…27b0
0x34b655…2a6f
2 touches
0 conflicts
0x4ef9fcf8…9572
0x34b655…2a6f
2 touches
0 conflicts
0x5060cdde…445d
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
0x966e45cf3c…9f0f25
Audit this contract →
← previous block
·
next block →
recent activity