pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,288,067
← previous block
next block →
recent activity
Analyzing
Block #95,288,067
12 transactions · 10 stateful · 2026-08-12 07:37:45 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
#95,288,067
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x000000b2
#2
executeBatch
#3
execFwdPositionOps
· blocks 1
#5
execFwdPositionOps
#6
forward
#7
updateDataFeedsValuesPartial
#8
updateDataFeedsValuesPartial
#9
transfer
#10
setData
#11
exactInputSingle
#4
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x91b0f8ed…6bd6
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd7
0x34b655…2a6f
4 touches
1 conflict
0x98bd7b25…3338
0x34b655…2a6f
4 touches
1 conflict
0x00ddbbf2…4588
0x34b655…2a6f
4 touches
1 conflict
0x17bbe4f8…08c5
0xe52b14…7230
2 touches
0 conflicts
0x3cebc8f1…975c
0xe52b14…7230
2 touches
0 conflicts
0x51232c8c…f30c
0xe52b14…7230
2 touches
0 conflicts
0x51232c8c…f30e
0xe52b14…7230
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
0x91b0f8edc5…b76bd6
Audit this contract →
← previous block
·
next block →
recent activity