pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,029,826
← previous block
next block →
recent activity
Analyzing
Block #96,029,826
13 transactions · 10 stateful · 2026-08-14 21:54:45 UTC
Parallelism
77
/100
Blocked
20
%
Avg conflicts / tx
0.23
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,029,826
· 13 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
0xab083028
#3
transfer
· blocks 2
#6
0x5acec890
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
0xc9623387
#10
execFwdPositionOpsV2
#11
execFwdPositionOpsV2
#12
setData
#4
transfer
· blocks 1
#5
transfer
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc4e19ae4…0788
0xe7cd86…c82d
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x889d5e90…929a
0x2a68ba…90c5
2 touches
0 conflicts
0x18010dbb…6b25
0x34b655…2a6f
2 touches
0 conflicts
0xa3a621f8…75a2
0x34b655…2a6f
2 touches
0 conflicts
0xaf811bc1…446c
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:
0xe7cd86e1…0fc82d
3 conflicts on slot
0xc4e19ae47e…dc0788
Audit this contract →
← previous block
·
next block →
recent activity