pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,531,075
← previous block
next block →
recent activity
Analyzing
Block #96,531,075
7 transactions · 6 stateful · 2026-08-16 15:56:12 UTC
Parallelism
57
/100
Blocked
33
%
Avg conflicts / tx
0.29
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,531,075
· 7 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execFwdPositionOpsV2
· blocks 1
#5
setData
#6
0x61d59c2d
#3
execFwdPositionOpsV2
· blocks 1
#4
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x37d710c8…45c1
0x34b655…2a6f
4 touches
1 conflict
0xaa3c398a…05d0
0x34b655…2a6f
4 touches
1 conflict
0xff196840…a453
0x34b655…2a6f
4 touches
1 conflict
0x0d3defdb…3dbe
0x34b655…2a6f
2 touches
0 conflicts
0x158becdc…73ed
0x34b655…2a6f
2 touches
0 conflicts
0x25191452…d2ed
0x34b655…2a6f
2 touches
0 conflicts
0x256a5318…6475
0x34b655…2a6f
2 touches
0 conflicts
0x31b39922…1e65
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
0x37d710c811…2145c1
Audit this contract →
← previous block
·
next block →
recent activity