pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,014,621
← previous block
next block →
recent activity
Analyzing
Block #96,014,621
10 transactions · 10 stateful · 2026-08-14 20:38:13 UTC
Parallelism
70
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,014,621
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xcbbdb31a
#2
execOrders
#3
execOrders
· blocks 1
#4
0x5acec890
#6
updateDataFeedsValuesPartial
#7
updateDataFeedsValuesPartial
#8
setData
#5
execFwdPositionOpsV2
· blocks 1
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4f97aa17…6776
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x31616f97…1acc
0x34b655…2a6f
4 touches
1 conflict
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0xe36fda9a…5e05
0x34b655…2a6f
4 touches
1 conflict
0x50a054d8…9506
0x34b655…2a6f
2 touches
0 conflicts
0x948836ff…59ab
0x34b655…2a6f
2 touches
0 conflicts
0xbde524f4…43bf
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
0x4f97aa17eb…2d6776
Audit this contract →
← previous block
·
next block →
recent activity