pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,304,714
← previous block
next block →
recent activity
Analyzing
Block #96,304,714
9 transactions · 6 stateful · 2026-08-15 20:57:24 UTC
Parallelism
78
/100
Blocked
17
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,304,714
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOpsV2
· blocks 1
#3
0xed82b078
#4
forward
#5
0xed82b078
#6
updateDataFeedsValuesPartial
#7
setData
#8
0x32366535
#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
0x7527177c…0520
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0xd077a617…2f11
0x34b655…2a6f
4 touches
1 conflict
0x354d5467…ea2b
0x34b655…2a6f
4 touches
1 conflict
0xa4e9800f…4ab0
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0x56a284d9…32e4
0x34b655…2a6f
3 touches
1 conflict
0x1fdab584…f092
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
0x7527177c52…2b0520
Audit this contract →
← previous block
·
next block →
recent activity