pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,337,512
← previous block
next block →
recent activity
Analyzing
Block #92,337,512
10 transactions · 10 stateful · 2026-08-01 23:48:23 UTC
Parallelism
80
/100
Blocked
30
%
Avg conflicts / tx
0.3
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,337,512
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execFwdPositionOps
· blocks 2
#4
verifyOracleProofV2
#5
forward
#6
execFwdPositionOps
#7
execOrders
· blocks 1
#9
setData
#2
execFwdPositionOps
#3
execFwdPositionOps
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w1
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0eac7709…66c3
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x35c16119…baf9
0x34b655…2a6f
4 touches
1 conflict
0x4caa7900…fd2e
0x34b655…2a6f
4 touches
1 conflict
0x64e5f38d…187c
0x34b655…2a6f
4 touches
1 conflict
0x7c0bdc54…9dde
0x34b655…2a6f
4 touches
1 conflict
0x7da79812…d73d
0x34b655…2a6f
4 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:
Perpl
1 conflict on slot
0x0eac770979…4766c3
Audit this contract →
← previous block
·
next block →
recent activity