pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,545,887
← previous block
next block →
recent activity
Analyzing
Block #89,545,887
13 transactions · 10 stateful · 2026-07-23 02:14:41 UTC
Parallelism
85
/100
Blocked
20
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,545,887
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
swap
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 2
#6
setData
#7
execOrders
#8
execOrders
#9
execOrders
#10
execOrders
#11
execOrders
#12
0xc7e3ec2c
#4
execFwdPositionOps
#5
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd68cd74f…9826
0x34b655…2a6f
4 touches
1 conflict
0x0413d1ed…ad55
0x34b655…2a6f
4 touches
1 conflict
0xb900efa2…8624
0x34b655…2a6f
4 touches
1 conflict
0x01a89030…f786
0x368ee5…7ca4
2 touches
0 conflicts
0x5b571ba0…f13a
0x368ee5…7ca4
2 touches
0 conflicts
0x68faa0b9…14af
0x368ee5…7ca4
2 touches
0 conflicts
0xcd621226…2df8
0x368ee5…7ca4
2 touches
0 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
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
0xd68cd74f55…fa9826
Audit this contract →
← previous block
·
next block →
recent activity