pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,556,718
← previous block
next block →
recent activity
Analyzing
Block #95,556,718
10 transactions · 8 stateful · 2026-08-13 06:13:37 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,556,718
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute_route
#2
0xd60faa87
#3
0xab083028
· blocks 1
#4
0x5acec890
#5
updateDataFeedsValuesPartial
#6
0x3f5c179b
#8
execFwdPositionOps
#9
setData
#7
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb2e3022c…8219
0x40c49f…2af0
4 touches
1 conflict
0x5d46e6a0…5ed9
0x40c49f…2af0
4 touches
1 conflict
0x76d1e78d…7877
0x40c49f…2af0
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x342fbbca…d443
0x40c49f…2af0
4 touches
1 conflict
0x389a56a6…986f
0x40c49f…2af0
4 touches
1 conflict
0xfecd07ed…6e13
0x40c49f…2af0
3 touches
1 conflict
0xd9610bfc…3b84
0x40c49f…2af0
3 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:
0x40c49f17…d22af0
1 conflict on slot
0xb2e3022c50…df8219
Audit this contract →
← previous block
·
next block →
recent activity