pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#92,275,986
← previous block
next block →
recent activity
Analyzing
Block #92,275,986
10 transactions · 9 stateful · 2026-08-01 18:38:57 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.2
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#92,275,986
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#2
execOrders
#3
execFwdPositionOps
#4
execFwdPositionOps
· blocks 1
#6
updateDataFeedsValuesPartial
#7
0x6a6e3db9
#8
setData
#9
0xc7e3ec2c
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda27c764…7fab
0x34b655…2a6f
4 touches
1 conflict
0xa4e9800f…4ab1
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0bd1061b…6f3f
0x34b655…2a6f
2 touches
0 conflicts
0x1356392e…f4a6
0x34b655…2a6f
2 touches
0 conflicts
0x3d1e509c…9368
0x34b655…2a6f
2 touches
0 conflicts
0x5cc477b5…1cf3
0x34b655…2a6f
2 touches
0 conflicts
0x5f453c44…fa94
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
0xda27c76455…2e7fab
Audit this contract →
← previous block
·
next block →
recent activity