pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,156,772
← previous block
next block →
recent activity
Analyzing
Block #96,156,772
8 transactions · 7 stateful · 2026-08-15 08:33:19 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,156,772
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOpsV2
· blocks 1
#4
execFwdPositionOpsV2
#6
execOrders
#7
setData
#5
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfcfc2ae3…972b
0x34b655…2a6f
4 touches
1 conflict
0x1d778644…7bb9
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x2ad2e6d1…e192
0x34b655…2a6f
2 touches
0 conflicts
0x7c09c53e…64b4
0x34b655…2a6f
2 touches
0 conflicts
0xa6176fff…d2c5
0x34b655…2a6f
2 touches
0 conflicts
0xa92fc25f…0349
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:
Perpl
1 conflict on slot
0xfcfc2ae3f6…f3972b
Audit this contract →
← previous block
·
next block →
recent activity