pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,654,961
← previous block
next block →
recent activity
Analyzing
Block #95,654,961
12 transactions · 11 stateful · 2026-08-13 14:27:46 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,654,961
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 1
#2
execOrders
#4
batchUpdate
#5
execFwdPositionOps
#6
0x927825be
#7
updateDataFeedsValuesPartial
#8
0x6a7dd4da
#9
transfer
#10
setData
#11
0x61d59c2d
#3
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x26e32e90…8827
0x34b655…2a6f
4 touches
1 conflict
0x90aa85ce…ab2d
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x43365261…c18b
0x34b655…2a6f
2 touches
0 conflicts
0x48a0f121…953b
0x34b655…2a6f
2 touches
0 conflicts
0x490f1ae9…a441
0x34b655…2a6f
2 touches
0 conflicts
0x5494779e…ed9b
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
0x26e32e90f9…688827
Audit this contract →
← previous block
·
next block →
recent activity