pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,587,960
← previous block
next block →
recent activity
Analyzing
Block #89,587,960
10 transactions · 9 stateful · 2026-07-23 06:55:42 UTC
Parallelism
70
/100
Blocked
22
%
Avg conflicts / tx
0.3
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,587,960
· 10 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
matchOrders
#2
0xab083028
#3
updateDataFeedsValuesPartial
#4
execFwdPositionOps
· blocks 2
#7
0x6a61bb65
#8
setData
#9
0xc7e3ec2c
#5
execFwdPositionOps
· blocks 1
#6
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
6
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x81e1b637…2b3b
0x34b655…2a6f
4 touches
1 conflict
0x6e19c9a0…7d86
0x34b655…2a6f
4 touches
1 conflict
0x81e1b637…2b3c
0x34b655…2a6f
4 touches
1 conflict
0xaca60768…7272
0x34b655…2a6f
4 touches
1 conflict
0x21e273cb…b384
0x34b655…2a6f
4 touches
1 conflict
0x39d46960…e3c0
0x34b655…2a6f
4 touches
1 conflict
0x69d0a300…67ef
0x34b655…2a6f
4 touches
1 conflict
0xa9f6f0bf…f882
0x34b655…2a6f
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
0x81e1b63766…662b3b
Audit this contract →
← previous block
·
next block →
recent activity