pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,396,093
← previous block
next block →
recent activity
Analyzing
Block #95,396,093
10 transactions · 8 stateful · 2026-08-12 16:44:54 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,396,093
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x3d9677…267b
#2
0x5acec890
#3
0x5acec890
· blocks 1
#4
updateDataFeedsValuesPartial
#6
execFwdPositionOps
#7
setData
#8
0x774f1e…9a1c
#9
0x59558d29
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66d5e476…8a1f
0x34b655…2a6f
4 touches
1 conflict
0x517157d5…68df
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x36890fff…f3d1
0x34b655…2a6f
2 touches
0 conflicts
0x3b299648…f5cf
0x34b655…2a6f
2 touches
0 conflicts
0x444eb03f…15d7
0x34b655…2a6f
2 touches
0 conflicts
0x4ce8861c…f862
0x34b655…2a6f
2 touches
0 conflicts
0x76dd4586…3cef
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
0x66d5e476c0…268a1f
Audit this contract →
← previous block
·
next block →
recent activity