pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#96,592,177
← previous block
next block →
recent activity
Analyzing
Block #96,592,177
10 transactions · 9 stateful · 2026-08-16 21:03:31 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#96,592,177
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrders
· blocks 2
#2
updateDataFeedsValuesPartial
#5
0x3f5c179b
#6
transfer
#7
setData
#8
0x61d59c2d
#9
execOrders
#3
execFwdPositionOpsV2
· blocks 1
#4
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0bbc9941…4358
0x34b655…2a6f
6 touches
3 conflicts
0x34b89870…ceb0
0x34b655…2a6f
4 touches
1 conflict
0xbef1e8f5…ae70
0x34b655…2a6f
4 touches
1 conflict
0xa7292c16…fca1
0x34b655…2a6f
4 touches
1 conflict
0x0f15f74f…8d72
0x34b655…2a6f
2 touches
0 conflicts
0x155e52ca…fac7
0x34b655…2a6f
2 touches
0 conflicts
0x38c586c5…2be6
0x34b655…2a6f
2 touches
0 conflicts
0x424934c8…f2f1
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
3 conflicts on slot
0x0bbc9941e2…c74358
Audit this contract →
← previous block
·
next block →
recent activity