pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,145,180
← previous block
next block →
recent activity
Analyzing
Block #96,145,180
6 transactions · 5 stateful · 2026-08-15 07:35:01 UTC
Parallelism
50
/100
Blocked
40
%
Avg conflicts / tx
0.5
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,145,180
· 6 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrder
· blocks 2
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOpsV2
· blocks 1
#5
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4f858307…7642
0x34b655…2a6f
6 touches
3 conflicts
0x681dd2e1…ce40
0x34b655…2a6f
6 touches
3 conflicts
0x1ac1c6bd…58eb
0x34b655…2a6f
6 touches
3 conflicts
0xa020506f…7c60
0x34b655…2a6f
4 touches
1 conflict
0x37bef14c…a6d5
0x34b655…2a6f
4 touches
1 conflict
0x77569532…a7c5
0x34b655…2a6f
2 touches
0 conflicts
0xec7d120d…7084
0x34b655…2a6f
2 touches
0 conflicts
0xfc371f5e…0955
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
3 conflicts on slot
0x4f858307b2…6c7642
Audit this contract →
← previous block
·
next block →
recent activity