pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,387,840
← previous block
next block →
recent activity
Analyzing
Block #96,387,840
8 transactions · 6 stateful · 2026-08-16 03:55:29 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,387,840
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOpsV2
#4
0x94defb17
· blocks 1
#6
execFwdPositionOpsV2
#7
setData
#5
0x94defb17
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
0x12b8914f…677d
0x968279…9342
4 touches
1 conflict
0x12b8914f…677e
0x968279…9342
4 touches
1 conflict
0x12b8914f…6781
0x968279…9342
4 touches
1 conflict
0x12b8914f…6782
0x968279…9342
4 touches
1 conflict
0x12b8914f…6784
0x968279…9342
4 touches
1 conflict
0x7c361f5f…89c5
0x968279…9342
4 touches
1 conflict
0x7c361f5f…89c6
0x968279…9342
4 touches
1 conflict
0x7c361f5f…89c8
0x968279…9342
4 touches
1 conflict
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:
0x96827978…f09342
1 conflict on slot
0x12b8914f8b…ea677d
Audit this contract →
← previous block
·
next block →
recent activity