pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,551,425
← previous block
next block →
recent activity
Analyzing
Block #95,551,425
11 transactions · 10 stateful · 2026-08-13 05:47:00 UTC
Parallelism
82
/100
Blocked
20
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,551,425
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute_route
#2
0xe33905c2
#3
0xab083028
#4
updateDataFeedsValuesPartial
#5
execFwdPositionOps
· blocks 1
#6
0x29eed2d3
· blocks 1
#9
0x6a7d5acb
#10
setData
#7
0x29eed2d3
#8
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w0
7
w1
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x5311f864…0984
0x754704…b603
4 touches
1 conflict
0xe225a8d6…5508
0x928dc8…8207
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x0aa28954…bf77
0x065c9d…c394
2 touches
0 conflicts
0x1ae7a08a…22b3
0x065c9d…c394
2 touches
0 conflicts
0xec805614…e946
0x065c9d…c394
2 touches
0 conflicts
0x11258774…9892
0x2a68ba…90c5
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
0xf3d10975b0…050d07
Audit this contract →
← previous block
·
next block →
recent activity