pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#89,587,851
← previous block
next block →
recent activity
Analyzing
Block #89,587,851
9 transactions · 6 stateful · 2026-07-23 06:54:58 UTC
Parallelism
78
/100
Blocked
17
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#89,587,851
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
matchOrders
#2
execPerpOps
#3
0x5a5d9a99
#4
aggregate3
#5
execFwdPositionOps
· blocks 1
#6
updateDataFeedsValuesPartial
#8
setData
#7
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x091164f5…6e32
0x34b655…2a6f
4 touches
1 conflict
0x9d6224fa…9986
0x34b655…2a6f
4 touches
1 conflict
0x9f4bc324…e6a6
0x34b655…2a6f
4 touches
1 conflict
0xba9f9225…2ead
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x091164f5…6e33
0x34b655…2a6f
4 touches
1 conflict
0x4e8d5fb8…f457
0x34b655…2a6f
4 touches
1 conflict
0x6e19c9a0…7d86
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
0x091164f59d…fd6e32
Audit this contract →
← previous block
·
next block →
recent activity