pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,073,197
← previous block
next block →
recent activity
Analyzing
Block #95,073,197
9 transactions · 8 stateful · 2026-08-11 13:27:58 UTC
Parallelism
56
/100
Blocked
38
%
Avg conflicts / tx
0.44
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,073,197
· 9 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
execOrders
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 1
#4
setData
#5
0x59558d29
#6
execOrders
· blocks 2
#7
execOrders
· blocks 1
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
7
w2
8
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x52010f20…7082
0x34b655…2a6f
4 touches
1 conflict
0x57be321f…fecc
0x34b655…2a6f
4 touches
1 conflict
0x62d6e82b…a750
0x34b655…2a6f
4 touches
1 conflict
0x78cbb28a…27c3
0x34b655…2a6f
4 touches
1 conflict
0x8fbde2b3…9b8f
0x34b655…2a6f
4 touches
1 conflict
0xd22dd5e8…83ff
0x34b655…2a6f
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:
Perpl
3 conflicts on slot
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity