pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,131,678
← previous block
next block →
recent activity
Analyzing
Block #96,131,678
12 transactions · 10 stateful · 2026-08-15 06:27:05 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,131,678
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xeabbe9d8
#2
0xf78cb219
· blocks 1
#4
0x6cfade05
#5
0x5acec890
#6
0x5acec890
#7
0x000000b2
#8
execFwdPositionOpsV2
#9
updateDataFeedsValuesPartial
#10
updateDataFeedsValuesPartial
#11
setData
#3
executePacked
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd3202dad…2628
0x065c9d…c394
4 touches
1 conflict
0x11258774…9892
0x2a68ba…90c5
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0ef74796…cd18
0x0a3323…0a3c
2 touches
0 conflicts
0x35a2c1ad…f105
0x0a3323…0a3c
2 touches
0 conflicts
0x52c63247…ce02
0x0a3323…0a3c
2 touches
0 conflicts
0x7ebd6e44…b6f3
0x6f4756…dd5b
2 touches
0 conflicts
0x3904724e…9a80
0x754704…b603
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:
Kuru Exchange: Market-MON/USDC
1 conflict on slot
0xd3202dad9b…3c2628
Audit this contract →
← previous block
·
next block →
recent activity