pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,825,098
← previous block
next block →
recent activity
Analyzing
Block #96,825,098
11 transactions · 10 stateful · 2026-08-17 16:35:01 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,825,098
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
execFwdPositionOpsV2
· blocks 1
#3
0x3f5c179b
#4
0x94defb17
· blocks 1
#7
updateDataFeedsValuesPartial
#8
commit
#9
setData
#10
execOrders
#5
0x94defb17
#6
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w0
5
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2e218554…6388
0x8964d7…10f8
4 touches
1 conflict
0x00000000…0008
0x8964d7…10f8
4 touches
1 conflict
0x2c14a354…9133
0x8964d7…10f8
4 touches
1 conflict
0x2c14a354…9134
0x8964d7…10f8
4 touches
1 conflict
0x2c14a354…9136
0x8964d7…10f8
4 touches
1 conflict
0x2e218554…6381
0x8964d7…10f8
4 touches
1 conflict
0x2e218554…6382
0x8964d7…10f8
4 touches
1 conflict
0x2e218554…6385
0x8964d7…10f8
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:
0x8964d7c9…5b10f8
1 conflict on slot
0x2e2185549b…106388
Audit this contract →
← previous block
·
next block →
recent activity