pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#95,557,884
← previous block
next block →
recent activity
Analyzing
Block #95,557,884
10 transactions · 8 stateful · 2026-08-13 06:19:29 UTC
Parallelism
80
/100
Blocked
25
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#95,557,884
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute_route
#2
0x6ad2e98b
#3
0x5acec890
· blocks 2
#4
0x5acec890
#5
execFwdPositionOps
#7
setData
#8
0xea714d…eaee
#6
execFwdPositionOps
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64f8554a…be61
0x34b655…2a6f
4 touches
1 conflict
0x733a5000…6e67
0x34b655…2a6f
4 touches
1 conflict
0xc01decc3…08a1
0x34b655…2a6f
4 touches
1 conflict
0x0e246445…9e0e
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x08d53462…97ef
0x2b46c0…1669
2 touches
0 conflicts
0x5a409e7f…09b6
0x2b46c0…1669
2 touches
0 conflicts
0x7a12283f…b18a
0x2b46c0…1669
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
0x64f8554ad2…e5be61
Audit this contract →
← previous block
·
next block →
recent activity