pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,316,371
← previous block
next block →
recent activity
Analyzing
Block #96,316,371
7 transactions · 7 stateful · 2026-08-15 21:56:03 UTC
Parallelism
57
/100
Blocked
29
%
Avg conflicts / tx
0.29
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,316,371
· 7 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrders
· blocks 1
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#6
setData
#2
execOrders
· blocks 1
#5
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x745a7fd6…5fea
0x34b655…2a6f
4 touches
1 conflict
0xa0d3a786…91d9
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x0eac6378…36f4
0x34b655…2a6f
2 touches
0 conflicts
0x19b4e3fd…3821
0x34b655…2a6f
2 touches
0 conflicts
0x21280422…0930
0x34b655…2a6f
2 touches
0 conflicts
0x24c1343e…9e0c
0x34b655…2a6f
2 touches
0 conflicts
0x2b648bb8…aade
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
0x745a7fd6fd…595fea
Audit this contract →
← previous block
·
next block →
recent activity