pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,507,345
← previous block
next block →
recent activity
Analyzing
Block #96,507,345
7 transactions · 7 stateful · 2026-08-16 13:56:51 UTC
Parallelism
71
/100
Blocked
14
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,507,345
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOpsV2
· blocks 1
#3
updateDataFeedsValuesPartial
#4
updateDataFeedsValuesPartial
#5
0x3f5c179b
#6
setData
#2
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xcea40325…6b39
0x34b655…2a6f
4 touches
1 conflict
0x3f5b9011…1bae
0x34b655…2a6f
2 touches
0 conflicts
0x4c4916e0…50eb
0x34b655…2a6f
2 touches
0 conflicts
0x4ec9ff52…e6f7
0x34b655…2a6f
2 touches
0 conflicts
0x640fd1c6…d624
0x34b655…2a6f
2 touches
0 conflicts
0x6c26d635…1bbf
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
0xbcbf5d09a8…c68bac
Audit this contract →
← previous block
·
next block →
recent activity