pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#87,361,676
← previous block
next block →
recent activity
Analyzing
Block #87,361,676
9 transactions · 9 stateful · 2026-07-12 22:45:48 UTC
Parallelism
78
/100
Blocked
11
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#87,361,676
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xab083028
#2
updateDataFeedsValuesPartial
#3
execFwdPositionOps
· blocks 1
#4
0x3f5c179b
#6
0x6a541993
#7
setData
#8
execOrders
#5
execFwdPositionOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22c2bb0c…9d5d
0x34b655…2a6f
4 touches
1 conflict
0x18ec97d9…6baa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x0ee13be7…7b2c
0x34b655…2a6f
2 touches
0 conflicts
0x15336fe3…1f37
0x34b655…2a6f
2 touches
0 conflicts
0x1a38937a…a582
0x34b655…2a6f
2 touches
0 conflicts
0x1b89bfcf…8505
0x34b655…2a6f
2 touches
0 conflicts
0x1b89bfcf…8506
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
0x22c2bb0c81…2b9d5d
Audit this contract →
← previous block
·
next block →
recent activity