pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,527,710
← previous block
next block →
recent activity
Analyzing
Block #95,527,710
10 transactions · 10 stateful · 2026-08-13 03:47:43 UTC
Parallelism
80
/100
Blocked
20
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,527,710
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 1
#2
execFwdPositionOps
#3
updateDataFeedsValuesPartial
#4
execOrders
· blocks 1
#6
updateDataFeedsValuesPartial
#7
setData
#8
0x59558d29
#5
execFwdPositionOps
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w0
5
w1
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x481b500f…7ef3
0x34b655…2a6f
4 touches
1 conflict
0xb9f50f91…13ef
0x34b655…2a6f
4 touches
1 conflict
0xbec23443…9293
0x34b655…2a6f
4 touches
1 conflict
0x1a5d321d…a474
0x34b655…2a6f
4 touches
1 conflict
0xd3cc5784…542b
0x34b655…2a6f
4 touches
1 conflict
0xb0c34bd7…259e
0x34b655…2a6f
3 touches
1 conflict
0x2697123c…8526
0x34b655…2a6f
2 touches
0 conflicts
0x6c3179e8…bfe9
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
0x481b500f8d…0c7ef3
Audit this contract →
← previous block
·
next block →
recent activity