pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,290,672
← previous block
next block →
recent activity
Analyzing
Block #96,290,672
11 transactions · 10 stateful · 2026-08-15 19:46:47 UTC
Parallelism
73
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,290,672
· 11 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xe33905c2
#2
0xab083028
#3
0xa96df62f
#4
0x41a8f47c
#5
0x5acec890
· blocks 1
#6
updateDataFeedsValuesPartial
#9
execFwdPositionOpsV2
#10
setData
#7
execFwdPositionOpsV2
· blocks 1
#8
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
8
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2e7a0c1d…caaf
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0x935a37fd…0514
0x34b655…2a6f
4 touches
1 conflict
0xa1210206…7aff
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x20317244…edb4
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x103de0…bb55
2 touches
0 conflicts
0x00000000…002e
0x59df86…2780
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
0x2e7a0c1d09…d7caaf
Audit this contract →
← previous block
·
next block →
recent activity