pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,154,495
← previous block
next block →
recent activity
Analyzing
Block #95,154,495
10 transactions · 7 stateful · 2026-08-11 20:16:56 UTC
Parallelism
70
/100
Blocked
29
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,154,495
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrders
#2
execOrder
· blocks 2
#3
execOrder
#4
execOrders
#7
updateDataFeedsValuesPartial
#8
setData
#9
0x053878…01e1
#5
execFwdPositionOps
· blocks 1
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1f94aad9…7ce0
0x34b655…2a6f
6 touches
3 conflicts
0x3c78ca04…432c
0x34b655…2a6f
6 touches
3 conflicts
0x4069c7ba…7c5b
0x34b655…2a6f
6 touches
3 conflicts
0x681dd2e1…ce40
0x34b655…2a6f
4 touches
1 conflict
0x845ec8b0…c1af
0x34b655…2a6f
4 touches
1 conflict
0x896bf7d8…906b
0x34b655…2a6f
2 touches
0 conflicts
0x94e4c632…46be
0x34b655…2a6f
2 touches
0 conflicts
0xa3a621f8…75a2
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
0x1f94aad974…0d7ce0
Audit this contract →
← previous block
·
next block →
recent activity