pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,664,667
← previous block
next block →
recent activity
Analyzing
Block #96,664,667
8 transactions · 5 stateful · 2026-08-17 03:08:06 UTC
Parallelism
75
/100
Blocked
20
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,664,667
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
handleOps
· blocks 1
#6
execFwdPositionOpsV2
#7
0x61d59c2d
#5
handleOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…000f
0x78999c…f371
4 touches
1 conflict
0xe0659a3f…90d9
0x000000…a032
4 touches
1 conflict
0x00000000…000b
0x754704…b603
4 touches
1 conflict
0x34b1e500…7687
0x754704…b603
4 touches
1 conflict
0x00000000…000b
0x78999c…f371
4 touches
1 conflict
0x1088dfef…9fc2
0x34b655…2a6f
2 touches
0 conflicts
0x19795ad6…4a16
0x34b655…2a6f
2 touches
0 conflicts
0x21170416…c384
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:
0x78999cc9…3cf371
1 conflict on slot
0x0000000000…00000f
Audit this contract →
← previous block
·
next block →
recent activity