pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#91,782,009
← previous block
next block →
recent activity
Analyzing
Block #91,782,009
11 transactions · 11 stateful · 2026-07-31 01:14:17 UTC
Parallelism
82
/100
Blocked
18
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#91,782,009
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
0x3f5c179b
· blocks 1
#4
0x3f5c179b
#6
execFwdPositionOps
· blocks 1
#7
execOrders
#9
setData
#10
0xc7e3ec2c
#5
batchUpdate
#8
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
6
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x46e558af…7871
0x34b655…2a6f
4 touches
1 conflict
0x810a3aa2…0227
0x34b655…2a6f
4 touches
1 conflict
0xa4e9800f…4ab0
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0xc2e36a04…b85e
0x851145…3f07
4 touches
1 conflict
0x41a7fe34…04fc
0x34b655…2a6f
4 touches
1 conflict
0xc1e685f7…7787
0x851145…3f07
4 touches
1 conflict
0x58c4164a…e0f6
0x851145…3f07
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:
Perpl
1 conflict on slot
0x46e558afdd…aa7871
Audit this contract →
← previous block
·
next block →
recent activity