pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,586,004
← previous block
next block →
recent activity
Analyzing
Block #95,586,004
12 transactions · 11 stateful · 2026-08-13 08:40:54 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,586,004
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrder
#2
0x5acec890
· blocks 1
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
#6
0x3f5c179b
#7
execFwdPositionOps
#8
0xed82b078
#9
0x6a7d838e
#10
setData
#11
0x59558d29
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xad919717…192e
0x34b655…2a6f
4 touches
1 conflict
0xfaf89f45…ced6
0x34b655…2a6f
4 touches
1 conflict
0xc53799eb…d928
0x34b655…2a6f
4 touches
1 conflict
0x038b9243…553d
0x34b655…2a6f
2 touches
0 conflicts
0x42b10c57…3ee7
0x34b655…2a6f
2 touches
0 conflicts
0x5fde4971…aac9
0x34b655…2a6f
2 touches
0 conflicts
0x8299fe6c…5752
0x34b655…2a6f
2 touches
0 conflicts
0x947bb79d…6458
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
0xad91971726…da192e
Audit this contract →
← previous block
·
next block →
recent activity